Am 23.06.2015 um 16:18 schrieb Ignacio Diaz-Emparanza:
El 22/06/15 a las 21:47, Sven Schreiber escribió:
> Am 22.06.2015 um 19:18 schrieb Riccardo (Jack) Lucchetti:
> ...
>> # with this, your original y is safe
>> moo()
> Safe yes, but of course at the cost of not getting any benefit at all (=
> the return value) from the function. I call this throwing the baby out
> with the bathwater. How on earth can this non-retrieval of the return
> value be considered a solution to the overwriting problem below, if the
> solution defeats the purpose in the first place???
Yes Sven, but this is the way in which all type of functions work, for
example,
<hansl>
function scalar a()
scalar b=2
return b
end function
nulldata 6
a()
</hansl>
the a() invocation does not save the result,
You almost had me there Ignacio, but not quite, because after your
function definition this line:
series look = log(a())
of course will work and use the call a() fruitfully. In fact, this
anonymous retrieval of the return value was exactly how this whole
discussion started, because *only* list-returning functions have been
the exception (since Feb 2015).
I will get back to the rest of your message later, right now I don't
have the time.
cheers,
sven