[Octave-bug-tracker] [bug #61673] classdef - (Access = hidden) results in spurious figure window

[Rik]

Update of bug #61673 (project octave):

                 Release:                  7.0.90 => dev                    

    _______________________________________________________

Follow-up Comment #5:

What are the semantics of the "Access = XXX" construct?  If XXX can only be a
string literal then we should probably enforce that requirement to prevent
weird errors like this.  On the other hand, if desired result is that you can
substitute a function which might do some calculations and then return one of
"public", "private", or "protected" then we should keep this behavior.

I have to say that the latter case seems quite strange.  It makes sense to me
to define classes at compile-time so you know in advance whether a method is
going to be public or private.  Using a function would allow the class to
change quite fundamentally based on runtime considerations.

I'll add jwe to this bug report for his opinion.  Also, I'll shift this to dev
since this won't get decided on in time for 7.1 release.

    _______________________________________________________

Reply to this item at:

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

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