Re: [Pharo-project] Symbolvalue:value:

2009-05-22 Thread Alexandre Bergel
I share the point made by Lukas. Symbolvalue:value: is very obscure. If we introduce Symbolvalue:value:, why not Symbolvalue:value:value: and so on? Alexandre On 21 May 2009, at 04:00, Stéphane Ducasse wrote: I would be in favor of having value: value: on symbol and get rid of value on

Re: [Pharo-project] Symbolvalue:value:

2009-05-22 Thread Damien Pollet
Maybe an alternative would be to use Helvetia to write blocks in shorthand. Currently, writing the whole [:each | each abs] is a bit of a pain, so the much shorter #abs is nice. But what if there was [… abs], the ellipsis meaning it or the argument, duh ? Several instances of … could be used in

Re: [Pharo-project] Symbolvalue:value:

2009-05-21 Thread Stéphane Ducasse
I would be in favor of having value: value: on symbol and get rid of value on Object Because this is really cool to write #( 1 2 3) collect: #abs On May 20, 2009, at 4:01 PM, Tudor Girba wrote: Hi, (I apologize for the length of this email, but I did not know how to write it shorter)

Re: [Pharo-project] Symbolvalue:value:

2009-05-20 Thread Lukas Renggli
Given that in Pharo we have Symbolvalue:, are there any reasons not to have also Symbolvalue: anObject value: anotherObject        ^ anObject perform: self with: anotherObject While Symbol#value: is at the border of being readable, Symbol#value:value: is even worse. It is not immediately

Re: [Pharo-project] Symbolvalue:value:

2009-05-20 Thread Stéphane Ducasse
do you have a scenario for it? And I agree with lukas about value on Object Stef On May 20, 2009, at 12:52 AM, Tudor Girba wrote: Hi, Given that in Pharo we have Symbolvalue:, are there any reasons not to have also Symbolvalue: anObject value: anotherObject ^ anObject perform: self

Re: [Pharo-project] Symbolvalue:value:

2009-05-20 Thread Gabriel Cotelli
+1 to the removal of value: from Symbol On Wed, May 20, 2009 at 3:18 AM, Lukas Renggli reng...@gmail.com wrote: Given that in Pharo we have Symbolvalue:, are there any reasons not to have also Symbolvalue: anObject value: anotherObject ^ anObject perform: self with:

Re: [Pharo-project] Symbolvalue:value:

2009-05-20 Thread Stéphane Ducasse
value from Object and value: from Symbol are different with value: on Symbol you can do self collect: #abs :) On May 20, 2009, at 2:48 PM, Gabriel Cotelli wrote: +1 to the removal of value: from Symbol On Wed, May 20, 2009 at 3:18 AM, Lukas Renggli reng...@gmail.com wrote: Given

Re: [Pharo-project] Symbolvalue:value:

2009-05-20 Thread Tudor Girba
Hi, (I apologize for the length of this email, but I did not know how to write it shorter) My reasons for Symbolvalue: and similar selectors are as follows. A Symbol is already used for several things, like a key in an identity dictionary. But it is also used for parameterizing a mapping to

Re: [Pharo-project] Symbolvalue:value:

2009-05-20 Thread Lukas Renggli
self collect: #abs Yes, that looks cool. However it is difficult to understand what it does for #(-2 3 4) - Does it collect the literal #abs for all the values of the collection? -- #(abs abs abs) - Does it collect the values of performing #abs on the collection? -- #(2 3 4) With

[Pharo-project] Symbolvalue:value:

2009-05-19 Thread Tudor Girba
Hi, Given that in Pharo we have Symbolvalue:, are there any reasons not to have also Symbolvalue: anObject value: anotherObject ^ anObject perform: self with: anotherObject ? Cheers, Doru -- www.tudorgirba.com Yesterday is a fact. Tomorrow is a possibility. Today is a