#class and #== optimalizations
ned at squeakland.org
Wed Jun 30 21:03:48 UTC 2004
On Wednesday 30 June 2004 2:38 am, Rob Withers wrote:
> One other class of methods that need consideration are those of the
> #ifTrue:ifFalse: varients. If the receiver isn't a boolean, you get a
> MustBeBoolean (or whatever it is) error. Tim mentioned this to me and
> said that changing these could have a noticable impact on the system. :-(
> Maybe we could change the MustBeBoolean to a msg send, like
> #cannotInterpret or doesNotUnderstand:. Then we could catch it. I
> haven't attempted any solution for this case.
Do you mean like Object>>mustBeBoolean ?
More information about the Squeak-dev