On Fri, October 13, 2006 15:57, Allin Cottrell wrote:
I agree on that. But I think Sven was talking about something a
bit different from executing a script, namely interactive work at
the console. I believe the question is: should interactive work in
the gui program (by point and click or via console commands) be
treated as a single "thread", or should there be a distinct
"console thread", with its own notion of "last model"?
Personally, I'm not sure about this, but I have tripped over the
issue myself once or twice. E.g. estimate a model in the gui,
open the console, type "genr uh = $uhat", and get an error message
because there's no $uhat available...
As far as I'm concerned, I'd rather have the present behaviour than
? ols y x
# do some random stuff in the gui
? genr u = $uhat
# get the wrong thing
My 2 cents go to the "2 threads" options.
Riccardo (Jack) Lucchetti
Dipartimento di Economia
Facoltà di Economia "G. Fuà"
Ancona