| Re: dependency tree / call graph in idl (cscope for idl)? [message #63801 is a reply to message #63673] |
Wed, 19 November 2008 13:08   |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
On Nov 19, 11:30 am, Sven Utcke <utcke+n...@informatik.uni-hamburg.de>
wrote:
> "mgal...@gmail.com" <mgal...@gmail.com> writes:
>> On Nov 19, 8:51 am, Sven Utcke <utcke+n...@informatik.uni-hamburg.de>
>> wrote:
>>> So what is the IDL-way of doing this?
>
>> There is nothing I know in IDL that would do this currently. The only
>> suggestion I have is to start a fresh IDL session. Compile the 79
>> files that you have so far
>
> Any easy< way to do that, as they are in several (sub) directories?
>
>> and then use RESOLVE_ALL. This will compile
>> routines that are called by the original 79 (and the routines that are
>> called by those routines, etc.). There should be messages in the
>> output log like "% Compiled module: ..." that should give an
>> indication of the needed routines. Of course, this is far short of a
>> call graph, but might serve depending on your requirements.
>
> It would at least tell me which routines I had missed so far, but
> alas:
>
> IDL> RESOLVE_ALL
> % Attempt to call undefined procedure/function: 'HALT'.
> % Error occurred at: RESOLVE_ALL_BODY 290
> /opt/products/idl/7.0/idl70/lib/resolve_all.pro
> % RESOLVE_ALL 351
> /opt/products/idl/7.0/idl70/lib/resolve_all.pro
> % $MAIN$
> % Execution halted at: $MAIN$
>
> Does not look to good, does it?
This is telling you that you are missing HALT. And furthermore,
halt.pro is not in your !path.
Mike
--
www.michaelgalloy.com
Tech-X Corporation
Associate Research Scientist
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
