[Octave-bug-tracker] [bug #41723] Local functions in classdef files

[John W. Eaton]

Follow-up Comment #3, bug #41723 (project octave):

I'm pretty sure the issue is that Octave is not expecting there to be anything
but comments and whitespace in the file after the END that matches CLASSDEF.

I didn't know that classdef files could define any functions outside of the
classdef block.

Fixing the parsing problem will be fairly simple.  Fixing the lookup rules so
that these functions behave as private functions that are only visible to
other functions defined in the classdef file will probably require more work.



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41723>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/