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

[Fernando]

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

Here is a partial fix, solving the problem described in the original
submission, but not the error in comment #11. I.e. it solves the first problem
I pointed out in my previous comment.

The patch simply takes into account that, if the indexing operation is in the
context of an assignment (or multiassignment), nargout should take its value
from the number of variables being assigned to, and not from the analysis of
the indexing expression.

(file #54549)

    _______________________________________________________

Additional Item Attachment:

File name: bug-63481-fix1.diff            Size:1 KB
    <https://file.savannah.gnu.org/file/bug-63481-fix1.diff?file_id=54549>



    _______________________________________________________

Reply to this item at:

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

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