[Pharo-project] why #ifNotNil: accepts parameter?
stephane.ducasse at inria.fr
Tue Jan 27 11:56:43 EST 2009
On Jan 27, 2009, at 5:04 PM, Esteban Lorenzano wrote:
> Very interesting stef, thanks a lot...
> but now, I'm not sure of what I did with OB-Tools (I just replace
> ifNotNil: [ :blah | ... ] with ifNotNilDo: [ :blah | ... ]... I
> understand why the first version of ifNotNil: is done like that in
> pharo... but what I do with compatibility? will pharo still support
> And, I also agree with lukas. blahDo: is ugly, if you have an elegant
> solution... but, what I have to do with OB-Tools? I replace methods
> (like before) or better I create a package OB-Tools-Squeak with
> extensions for Squeak?
> I know... this is hardly a "pharo issue", but maybe can provide pharo
> developers of clues of what to do if they are trying to keep
> compatibiity (I know, that's not a pharo goal -compatibility-, but
> sometimes may be necessary).
May be package extensions separately.
By accident have you seen the dates of the fixes proposed by vassili
this is not that long compared to the changes of compiled method that
we are waiting since at least 2001. So this is why changing is
But changing for better :)
> On 2009-01-27 13:09:30 -0200, Stéphane Ducasse
> <stephane.ducasse at inria.fr> said:
>> I found this blog entry really nice on this specific question.
>> On Jan 27, 2009, at 1:44 PM, Esteban Lorenzano wrote:
>>> I'm trying to understand why pharo modifies squeak behavior of
>>> ifNotNil: and introduces the optional parameter... is there a
>>> Pharo-project mailing list
>>> Pharo-project at lists.gforge.inria.fr
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev