reasons
- and:and:and: is only used in squeak totally not portable. (we could
live with that)
- and: is optimized by the compiler
- and:and: are not optimized
is it ok?
Stef
On May 26, 2010, at 10:10 AM, nullPointer wrote:
>
> But I don´t understand why the methods #and:and:and: AND #and:and:and:and:
> must be deprecateds... what is the equivalence now for that messages? is
> possible create a #&& and #|| messages?
>
> Regards
> --
> View this message in context:
> http://forum.world.st/and-and-and-deprecated-on-1-1-why-tp2230786p2231198.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
