Re: [Pharo-dev] strange error in latest 3.0 -

[Esteban Lorenzano]

yes, please :)

On 28 Jan 2014, at 13:47, Martin Dias <tinchod...@gmail.com> wrote:

> 
> So, what to do?
> - Don't send ClassModifiedClassDefinition in 
> SystemAnnouncer>>traitDefinitionChangedFrom: oldTrait to: newTrait ?
> - Implement Trait>>layout ?
> - Test for oldClassDefinition isTrait in 
> ClassModifiedClassDefinition>>isPropagating ?
> 
> 
> 
> I discussed with Camille and we think it's better this other alternative: to 
> fix class builder to only announce ClassModifiedClassDefinition for the class 
> that really changed its definition. For the subclasses, it won't be 
> announced. This way, it's not necessary to check if it is a propagation. We 
> can remove the two implementors and the unique sender. 
> 
> I verified that this was the behavior of "old class builder" (in Pharo 2). Do 
> you agree?
> 
> I can submit a slice this afternoon.
> 
> Martín