On Wed, 16 Dec 2009, Bert Freudenberg wrote:

> On 16.12.2009, at 03:11, David T. Lewis wrote:
>>
>> On Tue, Dec 15, 2009 at 08:35:55PM +0100, Levente Uzonyi wrote:
>>>
>>> We should definitely keep the tests. After a bit of googling I found
>>> Eliot's email which didn't get much attention:
>>> http://lists.squeakfoundation.org/pipermail/vm-dev/2009-September/003161.html
>>> This explains everything about mirror primitives. I wonder why these
>>> changes aren't integrated into VMMaker. (Note that ContextPart >>
>>> #objectClass: is missing from the attached source, I added an
>>> implementation to the trunk). I marked the failing tests as expected
>>> failures.
>>>
>>
>> Thanks for the pointer. I somehow completely overlooked this posting
>> on the vm-dev list. I opened a Mantis issue for "Add Mirror Primitives
>> to the VM" to track it.
>>
>>  http://bugs.squeak.org/view.php?id=7429
>>
>> Dave
>
>
> IIUC these new primitives break object encapsulation, which is fundamental change to the VM.

Most primitives already work like this in the current vm (at least the 
MirrorPrimitiveTests pass), 2 work but leave garbage on the stack 
(primitive 62 (#size) and 110 (#==)) and only one fails (primitive 
100 #perform:withArguments:inSuperClass:).

>
> Do we care?
>
> If so, do we still want them?
>

We have them in some way, so fixing them is a good idea.


Levente

> If yes, should there be a way to disable them, similarly to how we can disable file access?
>
> - Bert -
>
>
>