[Octave-bug-tracker] [bug #55768] display of classdef object should not show private or protected properties

[John W. Eaton]

Update of bug #55768 (project octave):

                  Status:             In Progress => Ready For Test         

    _______________________________________________________

Follow-up Comment #7:

I tracked this down to the evaluation of the expression happening in the
current stack frame (top level in this case) and that doesn't correspond to
the scope that is used when parsing the classdef object.  So the lookup of the
identifier 'true' could pick up some random value from the current frame.  In
my case, it was picking up the value of 'ans'.

I pushed the following changeset:

http://hg.savannah.gnu.org/hgweb/octave/rev/946c6f117091

As yet another issue, we could still intercept identifiers with names "true"
and "false" to avoid the possibility that someone has overloaded those
functions globally.  OTOH, if someone does that, then many other things will
also break, not just attribute values.

    _______________________________________________________

Reply to this item at:

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

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