| Re: Listing called functions in .pro file [message #7356] |
Mon, 11 November 1996 00:00 |
mallozzi
Messages: 60
Registered: August 1994
|
Member |
|
|
I have started the habit of adding a DEPENDENCIES clause to the header
of IDL routines. This seems to be an easy way to keep track things, and
easily lets others see what's needed to run your code.
-bob mallozzi
|
|
|
|
| Re: Listing called functions in .pro file [message #7362 is a reply to message #7356] |
Fri, 08 November 1996 00:00  |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
David Foster <foster@bial1.ucsd.edu> writes:
> Does someone have or know of a routine that can read an IDL .pro
> file and output a list of called external functions, possibly with
> their associated filenames?
>
> I often share programs with people, but I always forget to include
> necessary routines!
I would put the IDL routine RESOLVE_ALL in the program you wanted
to share. Enter IDL and run the program. All the unresolved routines will
be compiled and listed. Typing:
Help, /Source
will tell you what directory all those programs that got compiled
came from. Gather them up and ship them off.
I should think this would be a *tad* bit easier than writing your
own! But if you want something more elegant, start with the
RESOLVE_ALL code. It is written in IDL.
You wouldn't have any programs to do image reconstruction
you wanted to share would you David?
David
*************************************************
* David Fanning, Ph.D.
* 2642 Bradbury Court, Fort Collins, CO 80521
* Phone: 970-221-0438 Fax: 970-221-4762
* E-Mail: davidf@dfanning.com
*
* Sometimes I go about pitying myself, and all along my
* soul is being blown by great winds across the sky.
* -- Ojibway saying
************************************************
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
