| Re: Listing called functions in .pro file [message #7418 is a reply to message #7364] |
Tue, 12 November 1996 00:00   |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
MICHEL KRUGLANSKI <M.Kruglanski@oma.be> writes:
> The RESOLVE_ALL code does not resolve every thing.
> For instance, it does not work correctly when you make
> use of MAP_GRID. The MAP_GRID procedure does not exist;
> it is "created" by MAP_SET (see below)
>
> IDL> map_grid
> % Attempt to call undefined procedure/function: 'MAP_GRID'.
> % Execution halted at: $MAIN$
> IDL> map_set
> IDL> map_grid
Well "created" is not really the right word, I don't think.
MAP_GRID is a program module in the MAP_SET code.
This suggests to me that MAP_GRID was originally a
utility routine for MAP_SET that became a little more
useful than the author of the MAP_SET program originally
intended.
When utility routines become more generally useful like this
they are usually taken out of the original program and put
into a file of their own. In this case, the MAP_GRID code
should be taken out of map_set.pro and put into a file
named map_grid.pro. Then it could still be used by
MAP_SET *and* it could be used by any other program
that wanted to use it. (Including typing its name at
the IDL command line.)
More important for this discussion, it could then be
*found* by programs like RESOLVE_ALL using the
normal rules for automatic compilation that IDL uses.
Since the MAP_SET code is available to you in the IDL
library, you can do what the original author should have
done, and take the MAP_GRID portion out.
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
