> From: Juan Vuletich <
[hidden email]>
> Date: August 19, 2009 2:25:21 PM CEDT
> To: Stéphane Ducasse <
[hidden email]>
> Subject: Re: Cuis :)
>
> Hi Stef,
>
> Stéphane Ducasse wrote:
>> I spent some times and I will regularly continue to pay attention
>> that good fixes are integrated into pharo.
>> I would be interested in the textMorph cleans. Do you have them in
>> cs?
>
> You mean those in "Text cleanup and refactoring"? Yes... Just check
> the updated CategoriesAndChangeSets.txt. On each new release of Cuis
> I update it, and I also update the zip with all the changes.
>
>> Here is the list of my current inspection.
>>
http://code.google.com/p/pharo/wiki/CUISTreatedItems>
> Good! Just a couple of notes:
> - In "0207-AvoidCreatingDelays-jmv.1.cs Juan does not reset the
> waitDelay to 50ms, this is suspect..."
> Right. This was later fixed.
> - In "0213-ForkAnswersNil-jmv.5.cs Lukas was afraid it could break
> some code in external packages, so this change of API must be well
> documented if ever adopted."
> Code using the result value of #fork and friends is most likely
> already broken. It would be great to have an easy way to spot those
> users, but not having it, I prefer to move forward, and later fix
> buggy code. For instance, I'm integrating Shout into Cuis right now.
> Shout uses the returned value from #fork, so I had to fix it. So, it
> indeed breaks code in external packages, and you need to make a
> decision.
> - In " 0173-offList-jmv.1.cs Already in Pharo + class ProcessX ? +
> removeSelector #offList ", class ProjectX is the remains of class
> Project. Cuis does not support Projects.
Locked
