[Octave-bug-tracker] [bug #60280] nested method causes built-in function to be seen as a variable

[John W. Eaton]

Update of bug #60280 (project octave):

                  Status:                    None => Ready For Test         

    _______________________________________________________

Follow-up Comment #2:

I'm not sure which change fixed it, but after the following changes I made for
bug #60137 adn bug #60237, the example appears to work properly for me:


octave:1> classA().meth_a().meth_b([]);
ans = 1
'isempty' is a built-in function from the file libinterp/corefcn/data.cc
ans = 1
'isempty' is a built-in function from the file libinterp/corefcn/data.cc


http://hg.savannah.gnu.org/hgweb/octave/rev/0574c36a095e
http://hg.savannah.gnu.org/hgweb/octave/rev/c74ff452e2bb
http://hg.savannah.gnu.org/hgweb/octave/rev/34d06c73b48d

These changesets make changes in public interfaces, which is something that we
try to avoid during a stable release series.  OTOH, they are important to make
handles to nested and anonymous functions work properly.  And since handles to
nested functions were one of the big new features of Octave 6, I'm in favor of
making this change in version 6 even if it causes some (small) backward
compatibility issues.  These interfaces are not something that typical users
(even those who write .oct files) will encounter.

    _______________________________________________________

Reply to this item at:

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

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