[Pharo-dev] [pharo-project/pharo-core] 6f764a: 30830
henrik.s.johansen at veloxit.no
Thu Apr 24 09:19:00 EDT 2014
On 24 Apr 2014, at 2:24 , Marcus Denker <marcus.denker at inria.fr> wrote:
> On 24 Apr 2014, at 14:21, Sean P. DeNigris <sean at clipperadams.com> wrote:
>> GitHub wrote
>>> Log Message:
>> Which issues did this include?
> 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…
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…
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Pharo-dev