comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: .trace not working?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: .trace not working? [message #67584 is a reply to message #67582] Fri, 07 August 2009 10:44 Go to previous messageGo to previous message
penteado is currently offline  penteado
Messages: 866
Registered: February 2018
Senior Member
Administrator
On Aug 6, 10:40 pm, David Fanning <n...@dfanning.com> wrote:
> I debug in the Workbench, of course, so when I come to
> a stop I usually just step over routines to the next
> line of code (F6) or step into routines (F5). Or, if
> I want to run awhile, just put my cursor on the line
> I want to run to and type CNTL-R. I don't usually feel
> a need for anything fancier than that.

Same here. The workbench also has the debug view where I can see the
call stack, to know where the routines were called from (similar to
help,/traceback, but it is always shown and updated), and to move to
different scopes without moving the point where execution is stopped.
I can browse variable values in the variable view, or by just parking
the cursor over a variable name in the editor. And in the workbench,
console references to lines in the source code are links to show them
in the editor.

And yet I still frequently see people using just the command line,
editing source files in vi or emacs.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Plot multiple axes with log and linear scales
Next Topic: 3D UserSym?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 02:42:27 PDT 2025

Total time taken to generate the page: 0.64101 seconds