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

Home » Public Forums » archive » Re: Error handling by build-in IDL routines
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: Error handling by build-in IDL routines [message #14640] Tue, 16 March 1999 00:00 Go to previous message
Vapuser is currently offline  Vapuser
Messages: 63
Registered: November 1998
Member
"R.Bauer" <R.Bauer@fz-juelich.de> writes:

> Try this!
>
> PRO t2,test
>
> HELP,/recall,output=output
> for_test=(STR_SEP(output[1],','))[1]
> varsize=SIZE(routine_names(for_test,fetch=-1),/type)
> VarValue = Routine_Names(for_test, FETCH=-1 )
>
> IF test EQ varvalue THEN IF varsize NE 4 THEN $
> MESSAGE,'Expression must be of type FLOAT:'+for_test,/info
>
> END
>
> dd='dummy'
> t2,dd
>
> % T2: Expression must be of type FLOAT:dd
>
>
> R.Bauer


I don't think this work in a procedure.

If anyone out there in RSI land is listening...

It would be nice to have a function like the Perl package Carp.pm,
which reports errors from the line number of the invocation of Carp's
calling routine. So, say you have a perl routine foo which reports
some error by calling carp. The linenumber given in the error message
emitted by Carp is the line at which foo is called, not the line at
which Carp is called. That way, you can write error handling code that
doesn't have to keep track of the stack, and depend on the output from
help.
[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: block if
Next Topic: concat of %1 to a sav file

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

Current Time: Thu Oct 09 22:55:36 PDT 2025

Total time taken to generate the page: 1.91666 seconds