comp.lang.idl-pvwave archive: archive » Re: catch and I/O errors

Home » Public Forums » archive » Re: catch and I/O errors

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

Re: catch and I/O errors [message #42889 is a reply to message #42888]

Wed, 02 March 2005 14:35

Michael Wallace
Messages: 409
Registered: December 2003

Senior Member

> http://www.dfanning.com/misc_tips/conversion_errors.html

David's webpage says: 'The Catch documentation says that "all errors
that can be handled by IDL" can be trapped in this way.'

However, new and improved IDL documentation on Catch says : 'The CATCH
procedure provides a generalized mechanism for the handling of
exceptions and errors within IDL. Calling CATCH establishes an error
handler for the current procedure that intercepts all errors that can be
handled by IDL, excluding non-fatal warnings such as math errors.'

David, looks like it's time to get that secretary to do something! ;-)

Because the math errors are included in the non-fatal category, they
wound up grouped with the I/O errors. The I/O error handling was what
was needed for math errors, so the math errors just piggy-backed on the
same mechanism. Keep in mind that this is a wild and crazy guess based
on what I've seen. Someone correct me if I'm wrong. I really wish that
there were consistent error handling where you could differentiate
between the error types with a fatal/non-fatal flag or something similar.

-Mike

Report message to a moderator

[Message index]

		Re: catch and I/O errors By: David Fanning on Thu, 03 March 2005 09:11
		Re: catch and I/O errors By: David Fanning on Wed, 02 March 2005 16:59
		Re: catch and I/O errors By: Michael Wallace on Wed, 02 March 2005 14:35
		Re: catch and I/O errors By: David Fanning on Wed, 02 March 2005 14:05

Previous Topic:	IDL without X on Linux
Next Topic:	�D : XDA mini ��t�� XDA O2 IIs Wireless �^�� .............

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Dec 01 19:47:11 PST 2025

Total time taken to generate the page: 0.24690 seconds