On 29 Jun 2011, at 12:21, Olaf Till wrote:
> It occured to me that with your example the returns within the blocks
> weren't supposed to be met at all, but only
>
> Cell retval (rdims);
>
> ...
>
> return octave_value (retval);
>
> in the outer function block. And cell2cell should have nothing to do
> with Octaves workspace variables anyway. I'd guess that no mistake in
> the code of cell2cell caused the "garbling", and I don't have current
> tip of Octave installed ... maybe one could find a minimal example
> that triggers that possible bug in Octaves unstable version, but I'll
> probably won't have time for this at the moment.
>
> Olaf
The following code works fine for me
----------------
#include <octave/oct.h>
DEFUN_DLD (pippo, args, , "test return statement")
{
dim_vector rdims;
rdims.resize (2);
rdims(0) = 1;
rdims(1) = 1;
Cell retval (rdims);
return octave_value (retval);
}
----------------
so I still do not understand whee the problem lies.
I'll report back if I have time to look more into this,
but since my interest was in leasqr and not cell2cell itself,
it will be a very low priority task ...
c.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
