2010/8/24 Mariano Martinez Peck <marianopeck@gmail.com>


On Tue, Aug 24, 2010 at 2:58 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 23 August 2010 23:26, stephane ducasse <stephane.ducasse@free.fr> wrote:
> Hi guys
>
> I'm thinking aloud...
> I was wondering if we could not take advantage of a new class: Selector.
> MethodDict would only contain selectors and not symbols.
>
> I remember that I talked about that with hernan.
>

Hmm.. i don't see obvious advantages. Do you?
Most symbols (90% of cases), used as selectors, so it is likely that
such refactoring will be nothing more,
but just renaming the class :)

Personally I find it slightly annoying. �Symbols are only used as selectors by convention, and the VM has placed no restriction on what objects can be used as selectors so that, e.g. when aggressively shrinking one can replace Symbols with SmallIntegers. �Introducing a Selector class would obscure this possibility even more. �However I find use of the term "symbol" where "selector" is meant even more annoying. �I *hate* methodSymbol in MethodReference. �It should be selector.

2�
Eliot
�

Maybe because there are things implemented in Symbol or similar that are responsabilities of a Selector?

I have no idea. But I did a quick search and methods like flushCache, numArgs:,value:, isKeyword, cull:,� etc, seems more from Selector

�Cheers

mariano


> Stef
>
>
> _______________________________________________
> Pharo-users mailing list
> Pharo-users@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>



--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-users mailing list
Pharo-users@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project