Am 25.04.2013 17:31, schrieb Allin Cottrell:
After the change: as above, except that if we validate the obs
identifier we record it internally as a string, not a scalar.
Then when it comes to evaluating, e.g.,
scalar xt = x[1995:1]
we find the string "1995:1" which converts to an index in
situ. (This is OK since a string is in general acceptable as
an obs identifier.)
On the other hand, if we try to evaluate, e.g.,
foo = x(1995:1)
the form "x()", for x a series, leads us to expect a lag/lead
specification, which requires a scalar value. We find a string
where there ought to be a scalar, and we error out.
Sounds great, thanks.
-sven