| Re: Does anybody know an 'undocumented IDL feature' that does this [message #29015 is a reply to message #28940] |
Wed, 23 January 2002 15:27  |
Paul Hick
Messages: 9
Registered: November 1999
|
Junior Member |
|
|
Thanks for the pointer, Pavel. I never ran into RESOLVE_ALL before.
RESOLVE_ALL goes too far for my needs, I think. I don't really want a
recursive search. But RESOLVE_ALL calls ROUTINE_INFO; that looks like it
might do the job.
Pavel Romashkin wrote:
> RESOLVE_ALL, maybe? After a fresh restart, do Resolve_all, then get the list
> of compiled procedures. Not exactly the way you want it, but gives almost
> the same result.
> Pavel
>
> "Paul Hick" <pphick@ucsd.edu> wrote in message
> news:3C4E2CB3.50704@ucsd.edu...
>
>> Is there a way to get a complete list of function/procedure names that
>> any given IDL procedure needs to function properly? IDL has to do just
>> that when it reads a .pro file, and decides what to do with it. The
>> question is how to get to that information.
>>
>> Look at http://casswww.ucsd.edu/solar/help/pro_frames.htm to see what
>> I'm trying to do. For a given package of IDL procedures I'm trying to
>> get two pieces of related information:
>>
>> 1. which procedures does procedure A depend on;
>> 2. (more interesting) which procedures depend on procedure A.
>>
>> Given the first for all procedures in the package, I know how to get the
>> second. The first I now have to put in by hand as part of the
>> documentation, a somewhat boring and error-prone task. Would be nice to
>> get it automated.
>>
>> Any ideas?
>>
>>
>
>
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
