Teach Yourself Borland C++ in 14 Days - portal

NOTE
Using the Debugger
is highlighted in red. To clear the breakpoint, click on the stop sign icon and the breakpoint
is removed. You can also press F5 or choose Toggle Breakpoint from the Code Editor speed
menu to toggle a breakpoint on or off.
A breakpoint can only be set on a line that generates actual code.
Breakpoints are not valid if set on blank lines, comment lines, or
declaration lines. You are not prevented from setting a breakpoint on
these types of lines, but the debugger will warn you about the fact that
you have set a breakpoint on a line that contains no code. The following
lines will produce an invalid breakpoint warning:
// this is a comment followed by a blank line
int x; // a declaration
Breakpoints can be set on return statements or on the closing brace of
a function.
If you set a breakpoint on an invalid line, the debugger will warn you that the breakpoint may
not be valid, but it won’t do that until you attempt to run the program. Figure 11.1 shows
the warning message that is displayed when the debugger detects an invalid breakpoint.
Figure 11.1.
A warning message for
an invalid breakpoint.
If you click the Yes button in the warning dialog box, the program will run and any invalid
breakpoints will be ignored. If you click No, you will be taken back to the Code Editor, where
you can clear the invalid breakpoint. Any invalid breakpoints will be highlighted in green,
and the stop sign icon in the gutter will be grayed out.
When the program is run under the debugger, it behaves as it normally would—until a
breakpoint is hit, that is. When a breakpoint is hit, the IDE is brought to the top, and the
breakpoint line is highlighted in the source code. If you are using the default colors, the line
where the program has stopped is highlighted in red because red indicates a line containing
a breakpoint.
NEW TERM
The execution point indicates the line that will be executed next in your source code.
397
11