Daniel,

> Does it seem reasonable to you to use the #compilerClass hook to
> localize the effects of the Matrix hacks?

The changes are a true language extension. No previously valid
expression is now invalid. Some previously invalid expressions are now
valid and have a well-defined semantics. In that sense you can write
perfectly "compatible" code if that is what you are after. I can't see
any reason for why anyone would want to restrict the extensions to
certain classes.

Cheers,
  - Andreas

> -----Original Message-----
> From: squeak-dev-admin at lists.squeakfoundation.org 
> [mailto:squeak-dev-admin at lists.squeakfoundation.org] On 
> Behalf Of Daniel Vainsencher
> Sent: Thursday, December 05, 2002 9:27 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Re: Croquet alpha release(s?)
> 
> 
> On one hand, beating C++ performance at numeric stuff with 
> such a clean
> interface is surely nice. On the other hand, assuming most of the code
> in squeak remains very much unrelated to such things, I would 
> prefer to
> leave the default compiler (and even more so, the default syntax)
> unaltered.
> 
> Does it seem reasonable to you to use the #compilerClass hook to
> localize the effects of the Matrix hacks? I think of this as a less
> drastic plugin technology for a specific kind of performance critical
> code, similar to primitives. Or do you see Matrix operations becoming
> common to so many people that the two dialects would only be 
> confusing?
> 
> Daniel Vainsencher
> 
> "David A. Smith" <davidasmith at bellsouth.net> wrote:
> > PhiHo,
> > To that end, we will be incorporating our general purpose 
> > n-dimensional Matrix class which is intended to be used to 
> access the VPUs 
> > in a clean way.
> > 
> > David
>