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 on April 23, and its replacement, statalist.org is already up and running.


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

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


From   Stas Kolenikov <skolenik@gmail.com>
To   statalist@hsphsun2.harvard.edu
Subject   Re: st: Re: Listing user-written ado files called by program
Date   Wed, 7 Sep 2011 09:22:22 -0500

Partho Sakar and Nick Cox discussed how to make sure that third
parties can run user-contributed Stata packages installed on one's
computer when the do-files are shared.

On Wed, Sep 7, 2011 at 1:52 AM, Nick Cox <njcoxstata@gmail.com> wrote:
> Alternatively, teach your clients to use -ssc-.

I would second that. If you have a well-organized master do-file, it
would have a set-up stage at which all the referenced files should go.
At the very worst, you can always protect your non-official commands
in place with

capture listtab
if _rc == 199 ssc install listtab, replace
listtab <blah>

If you are super-serious about these compatibility issues, you could
run your master do-file with -adopath PLUS- being redirected to a
location where you'd collect all the third-party files for your
colleague/client, -captur-ing and -ssc install-ing them one by one, or
even on a virgin installation of Stata with no user-added files. You
could then either share the folder accumulated that way, or move all
the -ssc install- commands into the setup part of your do-file
sequence.

-- 
Stas Kolenikov, also found at http://stas.kolenikov.name
Small print: I use this email account for mailing lists only.
*
*   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