> A) it would be nice if one could "pipe" return values,
i.e. "return
> function()" is not a valid statement. This would make things more
> readable.
In principle you can. For example the following works OK:
<hansl>
function scalar fun2 (scalar x)
return 2*x
end function
function scalar fun1 (scalar x)
return fun2(3*x)
end function
eval fun1(2)
</hansl>
Can you give us a case where this sort of thing fails?
Hmm, perhaps it is only "void" which cannot be piped. "return null" is
also invalid in this case.
> D) If you create an empty bundle like "bundle new"
that is fine, but
> "bundle new = null" doesn't do anything, but neither report that.
I can't reproduce that:
Hmm, perhaps it was my mistake. I tried different things before and also made the error to
assign first an empty list to a bundle and then a series to the bundle, which changed the
element from a list to a copy of the series... Then I reread the manual and found my
mistake. Might be that I should have put it from the list
> F) I have frequent crashes when using the button to move the
output
> window to the front.
That's serious, but not something that anyone has reported before.
This is on Windows? In English or in German? (Not that that should make a
difference.) 64-bit or 32-bit build? (This may make a
difference.) And you're talking about the little "two windows" button that
pops down a list of gretl windows?
Yes, the little two windows button. gretl version 2017e-git, 64bit english
But I cannot reproduce it at will... I guess it is not something that happens with normal
usage. I changed a lot in many scripts and rerun them and had very long output windows
(using debug 2). Also, as Sven mentioned, I had two instances open. I will keep an eye on
it and try to reproduce it, the next time and report back.
Frederik