2008/9/22 Stéphane Ducasse <[EMAIL PROTECTED]>:
> Hi
>
> I would love if we could slowly deprecate caseOf:
>
This C-ism are built-in compiler optimization.
I would love, as well, to move all optimizations in separate class and
make it optional.
I see no real usage of #caseOf: or #caseOf:otherwise: in Pharo - just
in single place (ProcessBrowser).
However, i see a multiple places in Croquet image where it is used in a form of:
cmd := data at: 1.
cases := { .... }.
cmd caseOf: cases.
Which also proves that it not worth using it, because it can be simply
replaced by single line:
self perform: (cmdSelectors at: (data at:1) ) withPossibleArguments:
(Array with: data).
> Stef
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
--
Best regards,
Igor Stasenko AKA sig.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
