I can confirm a similar behaviour actually - even with latest cvs. Haven't been able
to figure out the exact source so far - that's why I haven't reported it yet.
Artur
Am 5. August 2015 18:47:00 MESZ, schrieb Sven Schreiber <svetosch(a)gmx.net>:
Am 05.08.2015 um 18:32 schrieb Wingenroth, Thorsten:
>
> I get the following error message:
>
>
>
>> set messages off
>
>>> # sample function call
>
>> nulldata 1800
>
> Sorry, this command is not available in loop mode
>
>
>
> Error executing script: halting
>
>> nulldata 1800
>
>
>
> But I am not in loop mode! And the command “nulldate” is not in the
> loop!
>
> To me, it seems that the loop is not finished when an error is
> raised.
>
Apart from the fact that it might be helpful to provide the version
number, yes I have experienced this behavior myself in the past. My
personal term for it is some remaining "flakiness" of gretl's command
interpreter. As you suggest, I think it comes from a previous script
that was aborted due to an error inside a loop. Then gretl continues to
think that the loop hasn't ended yet.
However, I'm not sure if this is still happening with recent versions,
I
think I haven't seen this recently. Again, please provide the version
you're using.
thanks,
sven
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.