On (26 Aug 95) rowan crowe wrote to Graeme Willox...



 rc>> The default for BCC is no debugging information.

 rc>> Hope this helps.



 GW> Thanks.  It did.  May I ask your expert opinion?  Don't you think it

 GW> would be better if I left debugging on while working with such

 GW> programmes as hello.c?



 rc> No, debugging information is really only for when you need to do very low

 rc> level debugging with something like Turbo Debugger. Low level as in

 rc> stepping through each individual ASM instruction that the compiler

 rc> generates.



dunno, I use td rather than the ide (see below) and I almost never

delve into assembler.



 rc> If you are just using the IDE and your program is well behaved (ie: may

 rc> have unexpected results but doesn't do naughty things like lock or reboot

 rc> the computer) then you should have no need to use Turbo Debugger.



Having written quite a few ill-behaved programs, I tend to use TD

rather than the IDE's debugger, mainly because the 386 version of

TD is much more resistant to crashes than the IDE.



TD also allows smarter breakpoints - eg break after the 1200th time

this loop is entered, or when j=124.



Cheers



--- PPoint 1.88