[squeak-dev] The Trunk: Chronology-Core-dtl.67.mcz

David T. Lewis lewis at mail.msen.com
Mon Jul 5 14:16:06 UTC 2021

Hi Marcel,

Thanks very much for fixing the update stream :-) I should have
thought to test it after making the change, after all the updater
is the very thing that is most sensitive to a change in DateAndTime now.


On Mon, Jul 05, 2021 at 09:22:41AM +0200, Marcel Taeumel wrote:
> Hi Dave, hi all!
> There was an update issue because a class definition will always be loaded before the updated methods, which meant that "DateAndTime now" stopped working after the classVar??InitializeFromPrimitive was removed, which was a problem because it apparently required during code loading.
> Using the update map (i.e. Monticello Configuration), I could solve this issue by first changing "DateAndTime class >> now" to not use??InitializeFromPrimitive any longer.
> So, there is no bigger issue here. Just an unexpected side effect with the MC code loading mechanism.
> Best,
> Marcel
> Am 03.07.2021 23:38:46 schrieb commits at source.squeak.org <commits at source.squeak.org>:
> David T. Lewis uploaded a new version of Chronology-Core to project The Trunk:
> http://source.squeak.org/trunk/Chronology-Core-dtl.67.mcz
> ==================== Summary ====================
> Name: Chronology-Core-dtl.67
> Author: dtl
> Time: 3 July 2021, 5:38:37.488688 pm
> UUID: 142336d9-cfb5-476e-ba15-a8daf9aad710
> Ancestors: Chronology-Core-dtl.66
> Cruft removal. DateAndTime no longer needs to be in the startUp list. The canInitializeFromPrimitive workaround is no longer needed. Do not use the no-argument call to primitiveUtcWithOffset, which works fine but is easier to understand in the image if we always use a single primitive interface.
> =============== Diff against Chronology-Core-dtl.66 ===============


More information about the Squeak-dev mailing list