| Re: resolve_all from inside a procedure? [message #77575] |
Tue, 13 September 2011 06:01 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Gianguido Cianci writes:
> I am trying to encourage my users to read the messages my
> code prints out, but they can get lost in a bunch of
> COMPILED system messages...
>
> The "solution" I have found is to have:
>
> compile_opt idl2
> resolve_all, /continue_on_error, unresolved=UR, /quiet
>
> right at the top. Now this seems to work in a practical sense.
> Just wondering how many years in hell it's going to cost me
> later, if any.
>
> Any thoughts?
If compile messages are what you are worried about, then
I would suggest spending more time in the morning
reading the newspaper. There may be one or two other
things that desperately need your attention!
What you could do, of course, is pre-compile your routines
and distribute them to your users as save files (*.sav).
IDL looks for *.sav files before it looks for *.pro files
when it needs something.
My experience with trying to "hide" things like this is
that it nearly always bites you in the ass. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
