Does #class deserve to be a very-special shortcut bytecode anymore?
Randal L. Schwartz
merlyn at stonehenge.com
Sat Jan 5 15:10:13 UTC 2002
>>>>> "Andreas" == Andreas Raab <Andreas.Raab at gmx.de> writes:
Andreas> In certain places it is critical that the class of an object cannot be
Andreas> forged. Otherwise you would need to know beforehand which methods you can
Andreas> send to proxies and which ones you don't. However, I agree that there's no
Andreas> need for having #class generate that byte code so some really long and
Andreas> annoying selector (like primitiveUnforgableClassOfObject) or somesuch might
Andreas> be in order.
Or "class" and "basicClass", following the "new" and "basicNew"
pattern, with ProtoObject defining class as "^self basicClass", and
basicClass spitting out the inline special bytecode, but class no
longer being a special.
--
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
|