On Thu, Mar 22, 2001 at 06:37:13PM +0000, [EMAIL PROTECTED] wrote:
> Useful as debuggers are, there are instances where print statements
> are the superior tool. If you are debugging code that has to interact
> with another process that is not under debugger control, and in a
> timely manner, then using a debugger may not be a viable option.
Use whatever you're comfortable with. I think Hamlet's totally spot-on
for the 'getting to grips with unknown code' scenario (although I also
don't see how an IDE helps find memory leaks) and class/property/method
inspectors are really useful. Being able to navigate between zillions
of files with a mouse and clicking on methods for some reason I really
like and still find hard to beat. (ctags just isn't the same..)
> > I think an excellent example of a solid, stable, and friendly debugger is
> > Metrowerk's Codewarrior's debugger. Call stack, view memory, watches,
CW rules. I'm pretty impressed with Borland's JBuilder too although you
need a decently fast machine since it's written in Java. Anyone played
with Borland's Kylix yet?
Real Men^WPeople debug with vi a.out :)
Paul, has an occasional fondness for debugging with syslog()
