Am 15.08.2020 um 02:28 schrieb Allin Cottrell:
On Fri, 14 Aug 2020, Sven Schreiber wrote:
>
> Run it for the first time, and gretl will complain about "end loop".
> Fine. Now comment out the two lines of the loop and run the script
> again; what I get is just an echo of the script lines with added ">"
> characters, but no other reaction or printout from the interpreter.
Although an error was flagged by the tokenizer, the state variable
indicating that the interpreter was in the process of compiling a loop
was not reverted -- so any further input was considered as part of an
unfinished loop.
That's now fixed in git.
Thanks, Allin. That made me think of a related thing; consider the
following pseudo script:
<broken-hansl>
loop 3
print "hey"
</broken-hansl>
If I run it, nothing happens. OK, I don't expect any (printed) output,
but wouldn't it maybe be better to throw an error if an end-of-file is
reached before the loop is completed with endloop?
cheers
sven