[Octave-bug-tracker] [bug #58695] Array is left empty if an element is a function call returning nothing

[John W. Eaton]

Follow-up Comment #17, bug #58695 (project octave):

I pushed two more changes for this bug:

http://hg.savannah.gnu.org/hgweb/octave/rev/ac7ab2a9018e
http://hg.savannah.gnu.org/hgweb/octave/rev/66397e171801

I have a draft patch to make function evaluations throw errors if functions
are called with too many inputs or requesting too many outputs.  It appears to
work properly for the simple tests like those from comment #11, but it causes
many failures in Octave's test suite:


Summary:

  PASS                            15771
  FAIL                              269
  REGRESSION                         23
  XFAIL (reported bug)               28
  SKIP (missing feature)             37
  SKIP (run-time condition)          14


I haven't checked in to any of these problems yet.  I suspect they are due to
being somewhat sloppy about the number of inputs and outputs for various
functions, like defining graphics callback functions with fewer inputs than
are provided when they are called (if they are not used in the function
anyway, then there is no real error, so...).  In any case, I think it is best
to make this change on default rather than stable.  I'll discuss further on
the maintainers list.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58695>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/