"hidden ivar" sounds like it would make understanding the system more complicated.�� What is its use-case?

On Tue, Jan 27, 2015 at 1:03 AM, Marcus Denker <marcus.denker@inria.fr> wrote:

On 24 Jan 2015, at 14:24, Marcus Denker <marcus.denker@inria.fr> wrote:


On 24 Jan 2015, at 11:24, Marcus Denker <marcus.denker@inria.fr> wrote:

Hi,

One of the power of slots is the concept of Virtual Slots that do not have an ivar to store their state.
But of course, some uses fo this concept want to store state in the object.
(e.g. imagine a property slot, all proper slots of the object would store into a property dictionary).

The idea is that one can add iVars reflectively that are hidden from both introspection *and* the class
definition. (the inspector should get ��a view to see reality, of course, similar to how we tread Dictionaries and OrderedCollection:
The ���basic��� view is not relavant in most cases, it is just available in addition, the default is the high level view that is closer
to the ���mental model��� of the programmer).


Ups, loading the Slice crashes the VM :-)
This kind of shows why doing these things in tiny, tiny steps is they way to go�����


ok, in 40463 AbstractInstanceVariableSlot will be renamed to IndexedSlot (so if you subclass it, you need to change the supeclass in your code)

Next: Hidden ivar

Marcus