Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-20 Thread Yuriy Tymchuk
On 20 Jun 2014, at 22:59, stepharo wrote: > > On 19/6/14 14:08, Henrik Johansen wrote: >> On 19 Jun 2014, at 1:42 , Yuriy Tymchuk wrote: >> >>> Hi, >>> >>> maybe we should implement #cull:cull: in symbol so that it will call >>> #cull:? Because this looks correct, if block has 1 parameter, t

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-20 Thread stepharo
On 19/6/14 14:08, Henrik Johansen wrote: On 19 Jun 2014, at 1:42 , Yuriy Tymchuk wrote: Hi, maybe we should implement #cull:cull: in symbol so that it will call #cull:? Because this looks correct, if block has 1 parameter, then #cull:cull: boils down to #value:, but when we have a symbol i

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread p...@highoctane.be
Le 20 juin 2014 02:16, "David T. Lewis" a écrit : > > On Thu, Jun 19, 2014 at 11:24:33AM -0300, Esteban A. Maringolo wrote: > > Can somebody please tell me the semantic difference between #cull: and #value: ? > > 'Cull' is not a word I ever used in any english based conversation :) > > Hi Esteban,

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread David T. Lewis
On Thu, Jun 19, 2014 at 11:24:33AM -0300, Esteban A. Maringolo wrote: > Can somebody please tell me the semantic difference between #cull: and > #value: ? > 'Cull' is not a word I ever used in any english based conversation :) Hi Esteban, I am an American English speaker, and I have never used t

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Chris Cunningham
A stretch for rational behind cull: We are 'culling' the excess variables passed to the block (roughly equivalent to killing animals when there are too many of them). On Thu, Jun 19, 2014 at 7:31 AM, Esteban Lorenzano wrote: > http://www.wordreference.com/es/translation.asp?tranword=cull > > y

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Esteban Lorenzano
http://www.wordreference.com/es/translation.asp?tranword=cull yet, it does not looks like having anything to do with executing a block with optional parameters :) On 19 Jun 2014, at 11:24, Esteban A. Maringolo wrote: > Can somebody please tell me the semantic difference between #cull: and >

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Esteban A. Maringolo
Can somebody please tell me the semantic difference between #cull: and #value: ? 'Cull' is not a word I ever used in any english based conversation :) Regards, -- Esteban. ps: I'm a big fan of having a "valuable" protocol, implemented by both Symbol and BlockClosure (and MessageSend), and I miss

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Yuriy Tymchuk
On 19 Jun 2014, at 15:47, Tudor Girba wrote: > In other engines where we want scripting to be used, we use a cull: or value: > with a prefix. In the case of Spec, this could be specCull:cull:. This could > be used as an extension of Symbol without spawning religious wars :). Yes, also I can u

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Tudor Girba
In other engines where we want scripting to be used, we use a cull: or value: with a prefix. In the case of Spec, this could be specCull:cull:. This could be used as an extension of Symbol without spawning religious wars :). The funny thing is that in all these engines that do define special value

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Yuriy Tymchuk
The thing is that cull:cull: can be used on block with 1 parameter. If you consider symbol as a block with one parameter then it will work in the same style. In other words: methods that use value:value: want to ensure that they are working with 2 param block. Methods that use cull:cull: don’t

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Henrik Johansen
On 19 Jun 2014, at 1:42 , Yuriy Tymchuk wrote: > Hi, > > maybe we should implement #cull:cull: in symbol so that it will call #cull:? > Because this looks correct, if block has 1 parameter, then #cull:cull: boils > down to #value:, but when we have a symbol instead, we have an exception. > >

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Yuriy Tymchuk
For example in Spec’s ListModel there is a thing called displayBlock:. And I have to write `list displayBlock: [ :package | package name ]`, while I think that `list displayBlock: #name` is clear enough, but the block receives #cull:cull: Uko On 19 Jun 2014, at 13:52, Sven Van Caekenberghe wr

Re: [Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Sven Van Caekenberghe
I believe this was already discussed long ago, with a decision not to go further that #cull: (or #value:) on Symbol, some even find that too much from a design perspective. I like writing code like #(1 2 3) collect: #asString especially interactively, since it is less verbose. In what situa

[Pharo-dev] Implementing cull:cull: in symbol

2014-06-19 Thread Yuriy Tymchuk
Hi, maybe we should implement #cull:cull: in symbol so that it will call #cull:? Because this looks correct, if block has 1 parameter, then #cull:cull: boils down to #value:, but when we have a symbol instead, we have an exception. I can open an issue and implement that stuff, but I want a feed