keep track of all libraries used [message #93358] |
Wed, 22 June 2016 20:43  |
hoiting2008
Messages: 4 Registered: March 2014
|
Junior Member |
|
|
I'm cleaning up my code and would like to keep track of all the functions and procedures (libraries and scripts) called under the main routine. Is there an easy way to know that?
Essentially what I want to know is what libraries I need to wrap up in the final package and what libraries aren't used and can be thrown away, before I zip everything and send the zip file to my colleagues.
I tried routine_info(/source) but it doesn't give me every routine I used, only those closer to the upper levels.
Thanks!
|
|
|
|
|
Re: keep track of all libraries used [message #93387 is a reply to message #93362] |
Wed, 29 June 2016 03:01   |
hoiting2008
Messages: 4 Registered: March 2014
|
Junior Member |
|
|
Perfect! That's what I'm looking for. Thanks!
On Saturday, June 25, 2016 at 11:51:53 AM UTC+10, andrew...@gmail.com wrote:
> On Thursday, 23 June 2016 13:13:24 UTC+9:30, hoiti...@gmail.com wrote:
>> I'm cleaning up my code and would like to keep track of all the functions and procedures (libraries and scripts) called under the main routine. Is there an easy way to know that?
>>
>> Essentially what I want to know is what libraries I need to wrap up in the final package and what libraries aren't used and can be thrown away, before I zip everything and send the zip file to my colleagues.
>>
>> I tried routine_info(/source) but it doesn't give me every routine I used, only those closer to the upper levels.
>>
>> Thanks!
>
> and to expand on Wayne's response,
>
> Resolve_all
>
> help,/source,out=routine_list
> help,routine_list
> ROUTINE_LIST STRING Array[nnn]
>
> So you end up with a string array giving the full filename of each source file.
> Now you just need a few lines of code to parse that array and copy those files into some distribution folder for zipping.
>
> Andrew
|
|
|
|