On Wed, Feb 12, 2003 at 12:21:42PM +0000, Jonathan Peterson wrote:
> Oh, agree that the fundamental things you do with a debugger are all
> there. It's more a case of how you like to do them. I like hovering my
> cursor over variables and seeing their current values in little
> tooltips. I like seeing a little pointer jumping around the code showing
> me what line is currently executing. I like setting breakpoints
Agreed. I patched a whole bunch of (non-OS X) things using
ProjectBuilder and loved its integration with gcc. Just being able to
click on files in the sidebar to load them was nice. In comparison I
find vi a pain, but then I probably don't know how to arbitrarily jump
between a set of files besides ctrl-^ and heavy use of screen(1)
> visually, not by knowing what line it is. And so on. I guess these boil
> down to the old graphical IDE vs not graphical IDE debate. But you'd
> have to agree that even die hard vi fans appreciate being able to see a
> terminal-full of their code at a time, rather than one line of it. Hence
> the ed comparison.
To add the fifth essential perl debugger command*, try 'w' to show
source around the current line. Useful for context. If you accidently
step ('s') into a sub use 'r' to continue and return from it.
Paul
* Shades of "stone soup"...
--
Paul Makepeace ....................................... http://paulm.com/
"If I was in the back yard, then the ferryman can at last cease his
ceaseless crossing."
-- http://paulm.com/toys/surrealism/
