[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: !ERR and MPFIT

Craig Markwardt (craigmnet@cow.physics.wisc.edu) writes:

> * to everybody: any suggestions on how to generically signal an error
>    condition?  My thoughts were:
>      - ERROR keyword variable - don't like this, since then the
>        function has to accept keywords
>      - define a new system variable - don't like this either, since
>        it's hard to do system variables right
>      - common block variable - not very pretty, but gets the job done.
> To be clear, this is some kind of error flag that a user routine would
> (optionally!) set to signal an abnormal termination condition.  Right
> now I am leaning toward the common-block approach.  Sorry David.

Oh, I like it. And to tell you the truth, this might
be the *perfect* situation for a common block. Just
don't be putting 'em in a widget program! :-)



David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: davidf@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155