Am 29.05.2013 17:23, schrieb Allin Cottrell:
On Wed, 29 May 2013, Sven Schreiber wrote:
If your returned bundle is not showing up in a window that
could be a bug in gretl, or possibly in your package (though
in the latter case you should get an error message, and it
would be a gretl bug if you don't). I'll try constructing a
minimal test of this functionality and report back.
I definitely didn't get any error message. There was indeed a mistake in
my bundle-print function (which is not literally called "bundle-print"
BTW), but it was strange that no error was triggered; I had the
following assignment
matrix m = <bundlename>.results
but the bundle member's real name was "mresults" instead. As I said, no
error message made its way through to me.
> One further suggestion for the packages: It would be nice if the
> bundle-print function (and friends) could get automatic access to the
> arguments with which gui-main was called. I know I can stuff all the
> arguments inside the bundle and read them out in bundle-print, but that
> seems redundant and clunky.
Not redundant, surely: if the information is to be used
subsequently it has to be stored somewhere. And I can't see a
superior alternative to storing it inside the package's
bundle. From gretl's point of view function arguments are
transient data. And consider the case where the bundle is
stored as part of a saved session file: how else could we save
the argument info other than in the bundle?
Ok, I guess you're right. I had thought of more "introspection"
capabilities, but it's true that for later use it's probably better to
really store it in the bundle.
thanks,
sven