I've just noticed that the old-style "=" boolean operator has been
deprecated already for 3.5 years (2017a). I suggest to declare it
illegal in the next release.
Somewhat related in terms of deprecation, I noticed the following
problem with the old-style (and illegal) "end loop" instead of
"endloop". Consider this script:
set verbose off
end loop # illegal
if "hey" == "hey"
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.
(Notice that even the "clear" at the top doesn't help.)
I'm wondering: Now with the geoplot addon in recent gretl versions we
have new file types understood by gretl, namely geojson and shape format
files. I guess it would be good if the file-open dialog could filter for
those files? (.json, .shp, perhaps .geojson)
I'm currently facing a problem running a function inside an MPI block,
when lists inside a bundle are used and accessed. (The context is the
johansensmall.gfn package, where the combination of exogenous terms and
running it under MPI fails.)
I'm not finished with the bughunting and want to try to produce a
minimal example, but I wanted to ask here already whether my suspicion
Because the MPI block doesn't inherit the dataset context of the calling
environment, for the bootstrap simulation I create a new dataset
environment via 'nulldata <...> --preserve'. In there I create the
simulated series. This works in principle. Am I right in assuming that
gretl is having problems when I use a previously packaged list like
mybundle.xlist and try to stuff it into the new dataset environment? I
have double-checked that $nobs matches the length of the variables in
the list, but is that enough?