Miranda getPropertySlot

__getPropertySlot/1 is a deprecated Miranda message.

Original Javadoc
Used in the expansion of 'foo::bar' so that this syntax represents foo's "bar" property.

'foo::bar' expands to 'foo.__getPropertySlot("bar").get'. When used an an lValue, 'foo::bar := newValue' expands essentially to 'foo.__getPropertySlot("bar").put(newValue)' except that the expansion also has the value of the assignment expression be the value assigned.

And finally 'foo::&bar' expands to 'foo.__getPropertySlot("bar")' The Miranda behavior provided here synthesizes, for foo's bar property, a Slot object  whose 'get</tt>' does a 'foo.getBar</tt>' <li>whose 'put(newValue)</tt>' does a 'foo.setBar(newValue)</tt>' <li>and whose 'isFinal</tt>' returns false</tt>'. </ul>

See also: Re: On kernel-E, operators, and properties (part 1)

Deprecated: Even if E does again decide to support explicit properties, it'll do it with a global function that asks the object's {@link #__getAllegedType} for the methods for its properties.

Issues
This protocol should probably be deprecated and removed, as it does not compose under inheritance. Thread: