Bookmark and Share

Notice: On March 31, it was announced that Statalist is moving from an email list to a forum. The old list will shut down at the end of May, and its replacement, statalist.org is already up and running.


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

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


From   Partho Sarkar <partho.ss@gmail.com>
To   statalist@hsphsun2.harvard.edu
Subject   st: Re: Listing user-written ado files called by program
Date   Wed, 7 Sep 2011 11:57:00 +0530

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
way!)

Thank you & best regards,

Partha S. Sarkar
*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   Site index