[Octave-bug-tracker] [bug #51754] MEX interface returns odd NULL objects

[John W. Eaton]

Follow-up Comment #4, bug #51754 (project octave):

I checked a set of changesets that should address this issue:

http://hg.savannah.gnu.org/hgweb/octave/rev/85488effc0ff
http://hg.savannah.gnu.org/hgweb/octave/rev/47c44b822d11
http://hg.savannah.gnu.org/hgweb/octave/rev/7662b441e2ea

The first should fix the problem with attempting to print undefined values
returned from functions.  It also considerably simplifies returning values
from functions, so I hope it improves performance, if only slightly.  It also
changes the behavior of Octave: now outputs that are not initialized in a
function are left undefined instead of being set to [].  And attempting to
assign an undefined value returned from a function is an error.  So I fixed
one place where that was a problem and also eliminated the now unused
Octave::undefined-return-values warning ID.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51754>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/