| IDL procedure "knowing its own name" [message #26425] |
Wed, 29 August 2001 02:37 |
mperrin+news
Messages: 81
Registered: May 2001
|
Member |
|
|
Let's say I'm running somethingorother.pro. Is there any way for the procedure
to itself determine that IDL is running a file called somethingorother.pro,
indeed, specifically /some/file/path/somethingorother.pro?
In more detail, what I've got is a script which processes a bunch of data
and produces some output which gets stored in a user-specified directory.
This script gets modified occasionally over time; it's useful to have a
copy of the script stored along with the data as a historical record so
that you can later look back and see exactly how the data was processed.
However, this tool is used on a number of different systems, and the
file path to the script varies from system to system. Right now I accomplish
this by hard-coding the path and name of the procedure as variables inside
the procedure, which means I have to change it by hand for each system.
Any ideas on how to automate this?
- Marshall
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
