Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

st: Re: Listing user-written ado files called by program

From   daniel klein <[email protected]>
To   [email protected]
Subject   st: Re: Listing user-written ado files called by program
Date   Wed, 14 Sep 2011 11:31:21 +0200

Thanks, once again, to Kit Baum, a new program ,-callsado-, is now
available from SSC. The program finds occurrences of ado-file names in
a do or ado-file. It is intended for programmers who lost track of the
user-written ado files called by their programs.

Note that -callsado- does not only find called ado-files, but all
occurrences of any ado-file's name in a file. The user will have to
decide, whether the program is acutally called in his file. While this
is still better than reading through the entire file yourself,
searching for called ados, you are probably best advised to avoid this
problem in the future.

To install the program type

. ssc inst callsado


--original message
This may be a common situation:

Like most Stata users, I have accumulated a number of user-written
programs (mostly downloaded from the SSC server, but also some other
sources).  In a program I have written, I implicitly use some of these
user-written programs via commands (e.g., rtfutil, listtab etc.).  I
have to share this program with other colleagues/clients, who
obviously will not have these downloaded programs.  So I would like to
include a note with my program listing all the user-written programs
which my program uses.  Since there are many of these, in several of
my sub-routines spread over do files, it would be quite tedious to
manually track them down one-by-one.  Any suggestions?

(I cannot just list all the user-written programs I have on my
computer, because I don't use them all in this program!   Also, even
finding which of the programs in my Stata ado path are user-written,
would be quite difficult, as -ssc install- puts them all in different
sub-directories, and after several updates, even the dates of the
files will not reveal their origin.  A brute force solution might be
to try and run my program on a computer with  Stata newly installed,
and checking the error messages.  I am hoping there may be some other

Thank you & best regards,

Partha S. Sarkar
*   For searches and help try:

© Copyright 1996–2018 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index