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

[A.R. Burgers]

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

The issue from comment #11 has been broken somewhere between 8.1.1 and 9.0.0.
With this script:


version
hg_id = __octave_config_info__.hg_id
cm = containers.Map;
cm('first') = tst_nargout;
ti = tst_nargout;
a_ti = ti.a_property

try
  ti = cm('first');
catch me
  fprintf('ti = cm(''first'') failed: %s\n', me.message);
end

try
  a = cm('first').a_property
catch me
  fprintf('a = cm(''first'').a_property failed: %s\n', me.message);
end

try
  if cm('first').a_property
    true
  end
catch me
  fprintf('if cm(''first'').a_property failed: %s\n', me.message);
end


works with 8.1.1


ans = 8.1.1
hg_id = 622985ce895b
nargout=1, s(1).type = .
a_ti = 1
nargout=1, s(1).type = .
a = 1
nargout=1, s(1).type = .
ans = 1


doesn't work with 9.0.0


ans = 9.0.0
hg_id = 630187b00ca2
nargout=1, s(1).type = .
a_ti = 1
a = cm('first').a_property failed: subsref: function called with too many
outputs
if cm('first').a_property failed: subsref: function called with too many
outputs




    _______________________________________________________

Reply to this item at:

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

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