On Sat, 12 Dec 2015, Sven Schreiber wrote:
Am 12.12.2015 um 21:06 schrieb Riccardo (Jack) Lucchetti:
> Sorry, Jab, but it looks as if there's an "endloop" missing (I could
> only count 3). That would explain why nothing runs: you'd still be
> inside the outermorst loop.
>
> what happens if you open a console and issue an "endloop" command?
>
Well spotted -- but shouldn't gretl notice that it's pointless to wait for
more commands at the end of the file and throw an error?
(I'm aware that end-of-file itself is not sufficient, due to run/include and
so on. But still.)
Good point.
In fact, there's a number of things we could do better (eg, optimize a few
things for speed) if we had a means to determine if a certain piece of
hansl code was meant to be run "on its own", so to speak.
In fact, this is what happens if you run a hansl file via "gretlcli -b".
Adding a warning like "warning: unterminated loop" is probably a good
idea.
-------------------------------------------------------
Riccardo (Jack) Lucchetti
Dipartimento di Scienze Economiche e Sociali (DiSES)
Università Politecnica delle Marche
(formerly known as Università di Ancona)
r.lucchetti(a)univpm.it
http://www2.econ.univpm.it/servizi/hpp/lucchetti
-------------------------------------------------------