comp.lang.idl-pvwave archive: archive » trapping type conversion errors

Home » Public Forums » archive » trapping type conversion errors

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

trapping type conversion errors [message #22314]

Wed, 01 November 2000 10:17

Vapuser
Messages: 63
Registered: November 1998

Member

I may be missing something, but are type conversion errors
untrappable?

Consider the following

PRO junk
catch,error
IF error NE 0 THEN BEGIN
message,!error_state.msg,/info
return
ENDIF

t = ['01','aa']
tt = fix(t)
;print,"I'm here"
;message,!error_state.msg,/info

help,!error_state,/st
END

From this snippet of code I conclude that the only way to 'trap' these
errors is to set !quiet=1 (just to get rid of the messages from the
interpreter) and then actually test the !error_state structure, either
the 'name' (=IDL_M_TYPCNVERR) or the 'code' (-97)

Am I wrong?

Am I alone in finding this a mite strange? Could we put in a request
that everything that sets !error_state.code to something != 0 be
trappable? Is there some reason, other than inertia, that this isn't
so that I just don't know about?

Also, math errors are only 'trappable' using 'check_math()', right?

whd
--
William Daffer: 818-354-0161: William.Daffer@jpl.nasa.gov

Report message to a moderator

[Message index]

trapping type conversion errors

By: Vapuser on Wed, 01 November 2000 10:17

Previous Topic:	Re: Array manipulation (typo fixed)
Next Topic:	Old Timers ??

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 15:29:20 PDT 2025

Total time taken to generate the page: 1.03973 seconds