Re: [Pharo-project] add return its argument

2010-05-10 Thread Norbert Hartl
I don't have time to scan the mailing list in detail. Was there any discussion that led to this change? Any pointers appreciated. I always thought the comfort of being able to chain selectors like add: outweighs the uniformity. Norbert On 08.05.2010, at 17:31, stephane ducasse wrote: if

Re: [Pharo-project] add return its argument

2010-05-10 Thread Stéphane Ducasse
consistency and this is linked to the work of nicolas to do the same in Squeak. Stef On May 10, 2010, at 10:06 AM, Norbert Hartl wrote: I don't have time to scan the mailing list in detail. Was there any discussion that led to this change? Any pointers appreciated. I always thought the

[Pharo-project] add return its argument

2010-05-08 Thread stephane ducasse
if somebody wants to check that the fixes I made are ok and that at:put: and add: return their arguments addReturnValue.1.cs Description: Binary data Stef___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr

Re: [Pharo-project] add return its argument

2010-05-08 Thread Lukas Renggli
That looks good to me. If no additional tests break after loading it, I guess it should be clear to integrate. It is important to have a uniform protocol. We should do the same for #nextPut: and #nextPutAll: Lukas 2010/5/8 stephane ducasse stephane.duca...@free.fr: if somebody wants to check

Re: [Pharo-project] add return its argument

2010-05-08 Thread Stéphane Ducasse
Tx! Soon in the update. On May 8, 2010, at 5:49 PM, Lukas Renggli wrote: That looks good to me. If no additional tests break after loading it, I guess it should be clear to integrate. It is important to have a uniform protocol. We should do the same for #nextPut: and #nextPutAll: Lukas