I just experienced a strange bug that disappeared when I changed all
lines containing just the name of a matrix, say beta_star (to print it,
like on p.70 of the manual), to an explicit 'print beta_star' line.
Before the change, gretl threw an error like "command 'beta_sta' not
known" (note the 8-char truncation).
What was especially strange was that the line 'beta_star' was coming
after an if-check that in this particular case was FALSE, and so the
syntax of the line should have been completely irrelevant. (And gretl
indeed did not execute the other statements in the if-block before the
Sorry, but I wasn't able to construct a small self-contained example, so
it seems relatively subtle. However I am pretty confident it is a bug
because as I said, with the explicit 'print xx' variant everything
*seems* to work now.
-- BTW, another unrelated thing: I still see the following in the first
line of a newly fired up gretl-console:
gretl-Konsole: geben Sie 'help' für eine Liste von Befehlen ein
Befehl 'elp' unbekannt
And while I'm at it, during function-debugging I often have to close and
restart gretl because it starts reporting nonsense errors (that go away
just by re-loading everything) after the first function error has
occurred. I know that's a pretty vague bug report, but it seems that
gretl may need to clean up its internals a little more after it
encountered a function error...
Anyway, I don't think these things should hold up a new release. Are
there still any other open issues? (Oh, apart from the shell-command
synchronicity thing on Windows... I will test that eventually.)