Ok, thanks for the reply, Allin. If it's not a bug and more or less
intended behavior, I am fine with it ;-)
Best,
Artur
Am 11.08.2017 um 15:27 schrieb Allin Cottrell:
On Fri, 11 Aug 2017, Artur Tarassow wrote:
> Dear all,
>
> I tried to run a script using the bash with the --scripopt option
> (latest git using ubuntu 17.04). The example script looks like:
>
> <hansl>
> clear # needs to be deactivated to work
> set verbose off
> scalar p = scriptopt
> print p
> </hansl>
>
> When the clear command is inserted, gretl stops saying
>
> <output>
>> p = scriptopt
> The symbol 'scriptopt' is undefined
> gretlcli: error executing script: halting
>> scalar p = scriptopt
> </output>
>
> Is this intended, or a bug?
I can't say it's specifically intended, but I don't think it's a bug.
The "clear" command instructs gretl to clear all data/variables from its
workspace, giving you a "blank slate"; since scriptopt is just a scalar
variable (albeit with a special mode of setting), it gets destroyed
along with everything else.
That said, if there's a good case for making an exception for scriptopt
we could consider that.
Allin