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

Re: st: Updating user-supplied code / mca example

From   Richard Williams <[email protected]>
To   [email protected], [email protected]
Subject   Re: st: Updating user-supplied code / mca example
Date   Tue, 07 Oct 2008 15:00:04 -0500

At 12:09 PM 10/7/2008, Sergiy Radyakin wrote:
Here are some of my thoughts, Allan:

-Version- statement must be correctly handled within the .ado file of
a particular command, and the resulting program must be tested with
the earliest Stata version with which it is claimed to be compatible.
Unfortunately this is not always the case (testing like that is often
omitted, because only one version of Stata is typically installed).

This is why I keep old versions of Stata installed. If I update one of my programs on SSC that currently works with Stata 8 or 9, I don't want to needlessly zap its functionality under those older versions. It is one thing to take advantage of major new features in Stata 10, but quite another to have your program break because some function got a new name in Stata 10. Luckily, Stata isn't that big as computer programs go, so keeping old versions around isn't that much of a problem. When I tweak my programs, I rerun some old do files under different versions of Stata to make sure I am still getting the same results and don't get errors.

Richard Williams, Notre Dame Dept of Sociology
OFFICE: (574)631-6668, (574)631-6463
HOME:   (574)289-5227
EMAIL:  [email protected]

*   For searches and help try:

© Copyright 1996–2024 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index