Teach Yourself Borland C++ in 14 Days - portal

400 Day 11
NOTE
In my opinion, the Add speed menu item is not very useful. It is much
easier to set a breakpoint in the Code Editor than it is to add a
breakpoint via the Add command in the Breakpoint list window.
Breakpoints can be enabled or disabled any time you like. You might disable a breakpoint
if you want to run the program normally for a while; you can then enable the breakpoint again
later without having to re-create it. Breakpoints that are disabled are ignored by the debugger.
If you want to modify a breakpoint, you can choose Properties from the primary Breakpoint
list speed menu. When you do, the Edit breakpoint dialog box is displayed. (See Figure 11.3.)
Figure 11.3.
The Edit breakpoint
dialog box.
The primary reason to modify a breakpoint is to add conditions to the breakpoint.
(Conditional breakpoints are discussed in the section “Conditional Breakpoints.”) The New
button in the Edit breakpoint dialog box works in a curious way. If you click the New button,
a breakpoint will be set on the line containing the cursor in the Code Editor. This is not a
particularly useful feature, so you can happily ignore the New button in the Edit breakpoint
dialog box.
To remove a breakpoint, you can select the breakpoint in the breakpoint list and then press
the Delete key on the keyboard. To delete all breakpoints, right-click the mouse to bring up
the secondary speed menu and then choose Delete All from the speed menu.
Now let’s take a look at the two breakpoint types.
Simple Breakpoints
Breakpoints can be either simple or conditional. A simple breakpoint will cause program
execution to be suspended whenever the breakpoint is hit. When you initially set a
breakpoint, it is, by default, a simple breakpoint. Simple breakpoints don’t really require
additional explanation. When the breakpoint is encountered, program execution pauses at
the breakpoint, and the debugger awaits your bidding. There’s no need to belabor the point.