On 24 Apr 2014, at 2:24 , Marcus Denker <marcus.den...@inria.fr> wrote:
> > On 24 Apr 2014, at 14:21, Sean P. DeNigris <s...@clipperadams.com> wrote: > >> GitHub wrote >>> Log Message: >>> ----------- >>> 30830 >>> >>> http://files.pharo.org/image/30/30830.zip >> >> Which issues did this include? >> > https://pharo.fogbugz.com/f/cases/13028/ > > I integrated it with a .cs as it did not work as a slice. > > I will rever 830, 831 and 832 (which is just that + reload of dirty + the > postscript for the change). > > But then we need to fix the issue of 13028… > > Marcus Maybe it’s just me, but isn’t it entirely wrong to fix subclasses being kept unmodified when a Shared Variable is added using change propagation? To me, it seems that mechanism is intended only to be used when a class change actually affects its subclass’ definition (iow, when Fields are modified...). I mean, it *should* be possible to setup the new class being migrated to with proper subclasses instvar, though I can’t exactly see where that is through all the layers of indirection… Cheers, Henry
signature.asc
Description: Message signed with OpenPGP using GPGMail
