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

Home » Public Forums » archive » Re: Error handing in embedded applications
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: Error handing in embedded applications [message #42950] Tue, 08 March 2005 10:47
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
Craig Markwardt writes:

> If your CATCH handler uses MESSAGE, perhaps that is confusing IDL?
> Could you avoid using a MESSAGE command? Perhaps you can reset the
> IDL !ERROR status code, or whatever it is these days, to zero?

I don't think I can avoid MESSAGE. It is the only way I know
to throw an error. I have tried setting the !Error_State fields
to "success" values, but to no avail. I think the problem is
that the error occurs during a widget event, and I think
the RSI routine that distributes events is catching the
error there somehow. I would LOVE to see some documentation. :-)

Cheers,

David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Re: Error handing in embedded applications [message #42959 is a reply to message #42950] Tue, 08 March 2005 06:41 Go to previous message
Craig Markwardt is currently offline  Craig Markwardt
Messages: 1869
Registered: November 1996
Senior Member
David Fanning <david@dfanning.com> writes:
> Folks,
>
> Does anyone understand error handling in embedded applications?
> I've got a bomb-proof program. CATCH error handlers everywhere.
> When an error occurs, I go to my error handling code. If in
> normal IDL, all is well, I return all the way back to the
> event loop level and I carry on, no big deal.
>
> In my embedded application, the same error gets into the
> CATCH, and then goes--apparently--to a different error
> handler where the words "Please consult the supplier of
> this application" is appended to the error message.

If your CATCH handler uses MESSAGE, perhaps that is confusing IDL?
Could you avoid using a MESSAGE command? Perhaps you can reset the
IDL !ERROR status code, or whatever it is these days, to zero?

Just some ideas,
Craig

--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@REMOVEcow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: looking for source of a caught runtime error.
Next Topic: Re: Regridding routines

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

Current Time: Fri Oct 10 17:10:53 PDT 2025

Total time taken to generate the page: 0.24051 seconds