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]

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

From   Christopher Baum <>
To   "" <>
Subject   Re: Re: st: new outreg and error code r(3499)
Date   Sat, 7 Apr 2012 09:16:05 -0400

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

> I think Bill Gould explained this (or part of this) three years ago:
> 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 Baum   |   Boston College Economics & DIW Berlin   |
                              An Introduction to Stata Programming  |
   An Introduction to Modern Econometrics Using Stata  |

*   For searches and help try:

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