[Octave-bug-tracker] [bug #63841] nargout is always 0 or 1 for subsref() in classdef methods

[Fernando]

Follow-up Comment #18, bug #63841 (project octave):

By the way, the title of the bug report could be changed, because nargout is
not always 0 or 1, as can be verified executing:


> A=tst_nargout;
> A{1:5}     % nargout=5
> A(1:5).a_property  % nargout=5


The title could say something like "nargout incorrect in assignments involving
subsref() for classdef methods".




    _______________________________________________________

Reply to this item at:

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

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