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

Home » Public Forums » archive » Re: Who called that procedure?
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: Who called that procedure? [message #64936 is a reply to message #64935] Wed, 04 February 2009 00:50 Go to previous messageGo to previous message
R.Bauer is currently offline  R.Bauer
Messages: 1424
Registered: November 1998
Senior Member
mgalloy schrieb:
> wlandsman wrote:
>> This is a minor problem but it has cost me a half-hour a couple of
>> times.
>>
>> I run RESOLVE_ALL to make sure that I am including all necessary
>> procedures when distributing software. One procedure may yield ~200
>> compiled supporting procedures, and I see one -- say obsolete.pro --
>> that should not be being used any more. So I want to know which of
>> the 200 procedures is still calling obsolete.pro. There does not
>> seem to be any pattern to the order of procedures displayed by
>> RESOLVE_ALL so that does not help. What would be nicest I suppose
>> would be a tree diagram of all the dependencies.
>>
>> In the end, I can simply grep the 200 procedures to see which one has
>> a call to obsolete.pro. But is there a better way? Thanks, -- Wayne
>
> I would like to add the creation of such dependency trees to IDLdoc at
> some point. In particular, they would be handy when giving the minimal
> amount of source to someone. Concerns about method calls,
> call_procedure/call_function/execute, and distinguishing a function call
> from an array indexing have always made me delay implementing it.
>
> I usually end up just searching (although I have replaced grep with ack,
> it conveniently ignores .svn directories and some other niceties to
> reduce the false positives).
>
> Another strategy is to put a "compile_opt obsolete" statement in
> MY_OBSOLETE_ROUTINE and then set:
>
> IDL> !warn.obs_routines = 1
>
> Now, calls to MY_OBSOLETE_ROUTINE will generate syntax errors when
> compiled (identifying their exact location in the error message).
>
> Mike

Is it something like this?

http://www.fz-juelich.de/icg/icg-1/idl_icglib/idl_source/idl _html/dbase/download/a_and_b_called_from.html

http://www.fz-juelich.de/icg/icg-1/idl_icglib/idl_source/idl _html/idl_work_libraries.htm

(look at the symbols with the arrow down)

May be I can extract the code then.

cheers

Reimar
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: fsc_field double
Next Topic: newbie here

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

Current Time: Wed Oct 08 17:30:14 PDT 2025

Total time taken to generate the page: 0.00360 seconds