comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » dependency tree / call graph in idl (cscope for idl)?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: dependency tree / call graph in idl (cscope for idl)? [message #63794 is a reply to message #63673] Wed, 19 November 2008 19:26 Go to previous messageGo to previous message
Craig Markwardt is currently offline  Craig Markwardt
Messages: 1869
Registered: November 1996
Senior Member
On Nov 19, 1:30 pm, Sven Utcke <utcke+n...@informatik.uni-hamburg.de>
wrote:
>
> 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?

Really you want to do something like,
RESOLVE_ALL, /CONTINUE, UNRESOLVED=unresolved

Then you will find out at the end if there are any unresolved
functions or procedures (they wil be stored in the 'unresolved'
variable.

Craig
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: loop for 365 days with 18 days interval
Next Topic: how can i get an [n,1] array without reform?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Dec 01 07:43:56 PST 2025

Total time taken to generate the page: 0.08331 seconds