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

Home » Public Forums » archive » Re: catch and I/O errors
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: catch and I/O errors [message #42873] Thu, 03 March 2005 09:11 Go to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
David Fanning writes:

> Good questions. I've forwarded them to the Book Club
> secretary. Perhaps we will get an answer. In the meantime,
> here is an article that pretty much exhausts what I know
> about the subject:
>
> http://www.dfanning.com/misc_tips/conversion_errors.html

OK, I'm trying to fix this, but I am running into semantic
problems.

According to the documentation, CATCH can catch any error
that occurs within IDL except "non-fatal warnings such
as math errors." My original understanding is that CATCH
could not catch input/output errors, and that a type
conversion error was a kind of input/output error.

But, I have verified that CATCH *can* catch normal input/output
errors. For example, you can catch the error of reading past
the end of a file. What it *can't* catch is type conversion
errors. So, using the elementary logic I learned in 8th grade,
a type conversion error must be a non-fatal math error.

All well and good EXCEPT that you can trap a type conversion
error with an ON_IOERROR condition, which would appear to
make it an input/output error. :-(

Anyone have any ideas about this?

Cheers,

David

--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: IDL without X on Linux
Next Topic: �D : XDA mini ��t����� �� XDA O2 IIs Wireless �^��� .............

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

Current Time: Mon Dec 01 15:06:20 PST 2025

Total time taken to generate the page: 1.12323 seconds