Re: Re: st: new outreg and error code r(3499)

[Christopher Baum <kit.baum@bc.edu>]

On Apr 7, 2012, at 2:33 AM, Richard wrote:

> 
> I think Bill Gould explained this (or part of this) three years ago:
> 
> http://www.stata.com/statalist/archive/2009-02/msg00648.html
> 
> In a nutshell, version control doesn't work when it comes to Mata 
> compilation. I think one solution is to actually do the compiling 
> using Stata 9.2 (if you still have a copy anyway). My memory is 
> vaguer on this, but I believe you can also just delete the compiled 
> libraries and let Stata recreate them, at least if you have provided 
> the original Mata code. I've never had to do this because I usually 
> have the latest version of Stata, but maybe somebody else can provide 
> the exact details.

Notwithstanding the complexities that Bill Gould described, it would be -very useful- to have a "mata mlib query' command that could identify the 
version of _Stata_ that was used to produce the contents of a mlib file. We have had this problem with SSC mlibs, including the mlib that Mark
Schaffer and I recently added to -ivreg2-: they have to be compiled on an earlier version of Stata if they are to be usable there, and given an mlib, 
there is no way of identifying whether it is compatible with an earlier version except trying to run it there (and unlike Richard, I don't have all the prior
versions sitting around on my machine). 

Kit

Kit Baum   |   Boston College Economics & DIW Berlin   |   http://ideas.repec.org/e/pba1.html
                              An Introduction to Stata Programming  |   http://www.stata-press.com/books/isp.html
   An Introduction to Modern Econometrics Using Stata  |   http://www.stata-press.com/books/imeus.html




*
*   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/