[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55768] display of classdef object should not

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #55768] display of classdef object should not show private or protected properties
Date: Sat, 15 Jun 2019 12:16:11 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

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:


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:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]