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

[John W. Eaton]

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

I looked over the latest patch (bug-63481-fix5.diff) and it seems reasonable
to me to use nargout = -1 to indicate that nargout is unknown.

Is it correct that this bug only affects the default branch, not stable?  If
so, then I think we can go ahead and push the change once it has a commit
message.

Small nit: the test file should probably not claim copyright for prior years
if it is a completely new file.

Thanks for all the work on this issue!


    _______________________________________________________

Reply to this item at:

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

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