| Re: Problem running functions [message #85883 is a reply to message #85881] |
Mon, 16 September 2013 10:40   |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Paul van Delst writes:
> Should it be:
>
> setenv IDL_PATH "${IDL_PATH}:+\$HOME/shdom/idl"
>
> ?
>
> You want to make sure you prepend (or append) the IDL_PATH to itself.
>
> Also, DavidF's comment about the order may be an issue. I take great
> pains to *not* have similarly named routines in different directories.
> But if you do have several versions of the same routines, not specifying
> a specific order may cause problems. I would recommend fixing that by
> having only one version of everything, but that may not be a
> workable/quick solution.
I'm really more concerned that she has a very long IDL path that was set
up for her and which she has little or no knowledge of. In such a case,
I would not be adding her files at the END of the path. Rather, I would
put them at the START of the path. That way, she at least has a chance
of getting her own files to compile properly, which was her original
concern, I think. Assuming, of course, she takes my advice about naming
things properly, using the right compile option, etc. She doesn't seem
inclined to. Old-school FORTRAN programmers often treat my advice like
this. ;-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
