#class and #== optimalizations

Andreas Raab andreas.raab at gmx.de
Wed Jun 30 20:54:35 UTC 2004

The trouble is that when you do this you need new VMs for pretty much every
proxy implementation. To me it makes much more sense to use DNU: instead of
VM lookup changes.

  - Andreas

----- Original Message ----- 
From: "Craig Latta" <craig at netjam.org>
To: <squeak-dev at lists.squeakfoundation.org>
Sent: Wednesday, June 30, 2004 10:36 AM
Subject: re: #class and #== optimalizations

> Hi Pavel--
> Rather than use doesNotUnderstand:, I think it makes more sense to
> modify method lookup in the virtual machine, and a few of the bytecode
> implementations. This has the additional benefit that it doesn't matter
> what the superclass of the proxy class is. An example set of VM changes
> is at http://www.netjam.org/squat/releases/current/bits/vmChanges.zip .
> The Squat snapshots have corresponding object memory changes.
> -C
> --
> Craig Latta
> improvisational musical informaticist
> craig at netjam.org
> www.netjam.org
> [|] Proceed for Truth!

More information about the Squeak-dev mailing list