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

Home » Public Forums » archive » listing all subroutines and paths used in a program.
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: listing all subroutines and paths used in a program. [message #74596 is a reply to message #74513] Mon, 24 January 2011 13:36 Go to previous messageGo to previous message
Andrew Cool is currently offline  Andrew Cool
Messages: 219
Registered: January 1996
Senior Member
On Jan 25, 7:06 am, Paulo Penteado <pp.pente...@gmail.com> wrote:
> On Jan 24, 6:51 pm, George Millward <george.millw...@noaa.gov> wrote:
>
>>> result = routine_info(my_app,/source)
>
>> % ROUTINE_INFO: String expression required in this context: MY_APP.
>> % Execution halted at: $MAIN$
>
> What is the contents of the variable my_app? Apparently, not a string,
> as routine_info expects.
>
> Anyway, it seems that you are looking for all currently compiled
> routines (after a call to your routine, or to resolve_all), which is
> done without providing a routine name to routine_info. That is,
> something like
>
> result=routine_info(/source)
>
> or
>
> result=routine_info(/source,/functions)


What's wrong with Help,/source ?

It gives the full path name for all compiled procedures and functions.


Andrew
www.skippysky.com.au
[Message index]
 
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: idl_help_path problem
Next Topic: Re: Need help with map projection conversion in ENVI

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

Current Time: Sat Oct 11 21:43:30 PDT 2025

Total time taken to generate the page: 0.24324 seconds