comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » IDLVM and retall

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: IDLVM and retall [message #50140 is a reply to message #50044]

Fri, 08 September 2006 10:10

JD Smith
Messages: 850
Registered: December 1999

Senior Member

On Fri, 08 Sep 2006 10:48:43 -0600, David Fanning wrote:

> Does your ERROR method provide a way of getting a traceback?
> That was my biggest problem with error methods. Sure, I could
> record and report the error, I just couldn't figure out where
> it was to fix the darn thing!!

I have a "debugging" switch in a menu I can turn on, and then instead
of just trapping and showing errors and unwinding the call stack, it
will halt at the error position (which IDLWAVE immediately highlights,
and lets you wander up and down the call stack), giving a traceback.

Only explicit calls to Error signal an error using this system. Other
braindead things (e.g. a[-1]=4) will cause a traditional halting
error, unless you go out of your way to trap it using CATCH. So
really the ERROR method is for convenient error reporting and
(potentially) recovering, not for automatic catching of all
conceivable errors (though it can be used that way).

JD

Report message to a moderator

[Message index]

		IDLVM and retall By: JD Smith on Mon, 04 September 2006 14:07
		Re: IDLVM and retall By: JD Smith on Fri, 08 September 2006 10:10

Previous Topic:	Re: IDLVM and retall
Next Topic:	errors-in-variables routin?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Oct 12 13:29:09 PDT 2025

Total time taken to generate the page: 1.68288 seconds