[Pharo-project] why #ifNotNil: accepts parameter?

Marcus Denker denker at iam.unibe.ch
Wed Jan 28 16:39:11 EST 2009

On 27.01.2009, at 17:56, Stéphane Ducasse wrote:

> 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
>> ifNotNilDo:?
>> 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
> 2007
> this is not that long compared to the changes of compiled method that
> we are waiting since at least 2001.

Wasn't that more like 1998?


Marcus Denker  --  denker at iam.unibe.ch

More information about the Pharo-dev mailing list