Eliminating superclass lookup in the VM (and dynamic composition of behavior)

Randal L. Schwartz merlyn at stonehenge.com
Wed Dec 11 15:54:45 UTC 2002


>>>>> "Stephen" == Stephen Pair <spair at acm.org> writes:

Stephen> Has this been done before?

I believe something like that was how "multiple inheritance" was managed
during that experimental period of the 60s^W80s...
a pseudo class was inserted in the chain containing methods from the
"other" non-traditional chain, and managed transparently.  When classes
were added to the "other" chain, they were copied into the pseudo-class.

I'd hate to have to update 15 entries every time I compiled something
in OrderedCollection, though.  Maybe run-time lookup isn't a bad
thing. :)

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!



More information about the Squeak-dev mailing list