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

[John W. Eaton]

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

I looked and I don't see anything to fix.  I don't see where we show any
examples of calling functions with more outputs than they produce and
expecting things to work.  Did I miss something?

If we want to document this behavior, then it seems like it belongs in more
introductory material or in the description of how functions or [x,y,...] =
foo () assignment statements work, not in the .oct and .mex file guide.

    _______________________________________________________

Reply to this item at:

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

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