Demystifying "most Smalltalk's don't directly support multiple inheritance"

Lic. Edgar J. De Cleene edgardec2001 at yahoo.com.ar
Fri Jun 23 10:50:28 UTC 2006


Klaus D. Witzel puso en su mail :

> Three things:
> 
> 1 - a way to access " thisContext sender ", " thisContext sender method ",
> " thisContext sender method literals " (this is in #switchSenderToParent:
> in my examples). inspect the three quoted expressions on Squeak and on the
> other VM and compare for differences. the literals must be accessible for
> read and write. this is usually the case when, since Smalltalk/2.x,
> support for the debugger is present (can do stack manipulation, code
> execution simulation, etc, all needed in support of a decent debugger). so
> these base functions exist for us for being reused :-)
> 
> 2 - a guarantee that the VM does indeed follow the Blue Book for super
> sends. the compiler knows this and puts the class in which a method was
> compiled into the method's last literal (you should have seen that when
> you inspected the above expressions), from where the VM then starts lookup
> when it interpretes the super send bytecode.
> 
> 3 - a means to make use of " [...] onDNU: #symbol do: [...] ". this is the
> classic #doesNotUnderstand: aMessage case wrapped into a convenient
> #onDNU:do: which either is already available in some form on the other VM
> or can be implemented to have the same functionality. my examples do not
> make use of any specific features of the exception passed to #onDNU:do:,
> so an implementation on another VM shouldn't be impossible.

I have something to follow and try, very very thanks.

Edgar



	
	
		
___________________________________________________________ 
1GB gratis, Antivirus y Antispam 
Correo Yahoo!, el mejor correo web del mundo 
http://correo.yahoo.com.ar 




More information about the Squeak-dev mailing list