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

Home » Public Forums » archive » Debugging overload
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: Debugging overload [message #88607 is a reply to message #88603] Fri, 16 May 2014 14:58 Go to previous messageGo to previous message
chris_torrence@NOSPAM is currently offline  chris_torrence@NOSPAM
Messages: 528
Registered: March 2007
Senior Member
On Friday, May 16, 2014 9:20:43 AM UTC-6, Fabien wrote:
> Hi again,
>
>
>
> I'll continue my whishlist with something more important. Consider the
>
> following program I'd like to debug:
>
>
>
> pro debugging_overload
>
>
>
> h = hash('key', INDGEN(10))
>
>
>
> a = mean(h['key']) ; Put a breakpoint here
>
>
>
> end
>
>
>
> With the breakpoint, the program stops and I usually tip F5 (shortcut
>
> for "step-into" in the debugger). Due to the operator overloading, the
>
> "step into" is now requiring 31 (!) clicks:
>
>

Can't you just do F6 or hit the Step Over button instead? Other than the fact that you can't see the pro code, I don't see much difference between this and stepping into something like "dist.pro". Also, even if you do accidentally step into a save file, you can hit F7 (Step Out) to immediately get back out.

Finally, in IDL 8.3.1 we are going to report line numbers for save files. This doesn't do you any good in this case (since you don't have the pro code) but for your own save files you might actually want to step through them as a save file but see the line numbers.

Cheers,
Chris
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Common block conumdrum
Next Topic: Coyote NCDF_FILE object to read HDF

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

Current Time: Wed Oct 08 18:03:38 PDT 2025

Total time taken to generate the page: 0.00178 seconds