| Using idlrt.exe [message #31374] |
Wed, 10 July 2002 10:58  |
notspecified
Messages: 14
Registered: February 2002
|
Junior Member |
|
|
We've succeeded, with various hoo-doo spells and leaps of imagination,
to run .sav files without the IDL interpreter interface-- But we have
a lingering feeling that it would be nice to have some documentation.
Or at least some assurance that our .sav routines will continue to
work in runtime IDL versions-to-come... -Is- there actual
documentation for idlrt.exe anywhere (assuming that this is, in fact,
how the trick is done)? Does anyone have reliable knowledge about how
it all works?
Matt Feinstein does not include his email address
in the text of usenet postings.
--------
Harvard Law of Automotive Repair: Anything that goes away
by itself will come back by itself.
|
|
|
|
| Re: Using idlrt.exe [message #31469 is a reply to message #31374] |
Wed, 10 July 2002 14:27  |
R.Bauer
Messages: 1424
Registered: November 1998
|
Senior Member |
|
|
Matt Feinstein wrote:
>
> We've succeeded, with various hoo-doo spells and leaps of imagination,
> to run .sav files without the IDL interpreter interface-- But we have
> a lingering feeling that it would be nice to have some documentation.
> Or at least some assurance that our .sav routines will continue to
> work in runtime IDL versions-to-come... -Is- there actual
> documentation for idlrt.exe anywhere (assuming that this is, in fact,
> how the trick is done)? Does anyone have reliable knowledge about how
> it all works?
>
> Matt Feinstein does not include his email address
> in the text of usenet postings.
> --------
> Harvard Law of Automotive Repair: Anything that goes away
> by itself will come back by itself.
Dear Matt,
there is a small amount of rules you should know.
* !PATH does not exist in runtime
* the filename of the routine have to be the same as
the calling procedure.
* EXECUTE won't work (e.g. read_ascii uses EXECUTE)
* nothing could be compiled but other compiled routines
could be loaded.
This means you can separatly build runtime modules
for each routine or one for a routine with all dependent
routines.
* if a compiled routine is in the search path then this
routine is loaded instead of compiling the source by
working with the interpreter.
* calling is idl -rt=./my_runtime.sav
All routines of our library are compiled by this routine:
http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_source/idl _html/dbase/download/compile.tar.gz
for example
url_get -o x_def_colortable.sav
http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_source/idl _html/dbase/download/x_def_colortable.sav
idl -rt=./x_def_colortable
Further routines you find at
http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_lib_intro. html
regards
Reimar
--
Reimar Bauer
Institut fuer Stratosphaerische Chemie (ICG-I)
Forschungszentrum Juelich
email: R.Bauer@fz-juelich.de
------------------------------------------------------------ -------
a IDL library at ForschungsZentrum Juelich
http://www.fz-juelich.de/icg/icg1/idl_icglib/idl_lib_intro.h tml
============================================================ =======
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
