Am 18.04.2017 um 17:12 schrieb Sven Schreiber:
Am 14.04.2017 um 20:23 schrieb Allin Cottrell:
> However, here's a possibly semi-relevant point: when "include" is used
> in a script with a gfn argument (only), gretl checks to see if the
> function package in question is already loaded, and if so the package
> file is not re-read. I've just added a --force option for "include"
> which will force re-reading from file regardless.
Just a feedback that this new --force option is very useful when
testing/debugging packages!
And I just had an example where I replaced the old version of a function
package with a new one (unzipped zip into gfn et al.). By looking
directly into the gfn with a text editor I made sure it was the new
version (had changes).
And then in the GUI (with 2017a on Windows) I chose in the
function-package list window the corresponding directory (via the folder
button), which showed me the package. Then right-clicking and opening
the info script I got the old (outdated) content.
So I think gretl is not --force-reloading the package file when I
manually select a package location; perhaps it should.
thanks,
sven