Hi everyone,
I've ported some of my code into Squeak 4.3 (was running in 4.2 before), and ran into a weird issue comparing Date objects.
When you execute "Date today", it produces a Date object with DateAndTime localTimeZone's offset, which is set upon image startup to be Locale >> offsetLocalToUTC, which in turn calls Locale >> primTimezone.
On a 4.2 image, on both my XP and Windows 7 machines, that primitive returns -300 (minutes), which is -5 hours, which is correct (since I live in SW Ontario, Canada, which is EST).
On a 4.3 image, with or without updates, that method returns -240, which is -4, which is clearly wrong at this point in time.
- Jon
Actually, some additional information...
Turns out the 4.2 testing I was doing was with the Cog VM. With the normal 4.2 VM (which is the same as the 4.3 VM), the problem shows up in 4.2 also.
So this appears to be an issue with the latest Windows VM, which is Squeak4.1.1 from Jul 27, 2010...
- Jon
On Tue, Jan 31, 2012 at 11:12 AM, Jon Hylands jon@huv.com wrote:
Hi everyone,
I've ported some of my code into Squeak 4.3 (was running in 4.2 before), and ran into a weird issue comparing Date objects.
When you execute "Date today", it produces a Date object with DateAndTime localTimeZone's offset, which is set upon image startup to be Locale >> offsetLocalToUTC, which in turn calls Locale >> primTimezone.
On a 4.2 image, on both my XP and Windows 7 machines, that primitive returns -300 (minutes), which is -5 hours, which is correct (since I live in SW Ontario, Canada, which is EST).
On a 4.3 image, with or without updates, that method returns -240, which is -4, which is clearly wrong at this point in time.
- Jon
Hi Jon,
I am not using a Windows VM, and am in the EST time zone, so I cannot directly reproduce your problem. But I'm very interested in knowing the cause of it if you or anyone else figures it out. In particular I'd like to know if it's a VM issue or an image issue (or both).
Dave
On Tue, Jan 31, 2012 at 11:26:57AM -0500, Jon Hylands wrote:
Actually, some additional information...
Turns out the 4.2 testing I was doing was with the Cog VM. With the normal 4.2 VM (which is the same as the 4.3 VM), the problem shows up in 4.2 also.
So this appears to be an issue with the latest Windows VM, which is Squeak4.1.1 from Jul 27, 2010...
- Jon
On Tue, Jan 31, 2012 at 11:12 AM, Jon Hylands jon@huv.com wrote:
Hi everyone,
I've ported some of my code into Squeak 4.3 (was running in 4.2 before), and ran into a weird issue comparing Date objects.
When you execute "Date today", it produces a Date object with DateAndTime localTimeZone's offset, which is set upon image startup to be Locale >> offsetLocalToUTC, which in turn calls Locale >> primTimezone.
On a 4.2 image, on both my XP and Windows 7 machines, that primitive returns -300 (minutes), which is -5 hours, which is correct (since I live in SW Ontario, Canada, which is EST).
On a 4.3 image, with or without updates, that method returns -240, which is -4, which is clearly wrong at this point in time.
- Jon
I seem to recall that Eliot had a different idea of how the time zone support should work. The image code hasn't changed in a while so I'm pretty sure it's a VM issue.
- Bert -
On 31.01.2012, at 17:49, David T. Lewis wrote:
Hi Jon,
I am not using a Windows VM, and am in the EST time zone, so I cannot directly reproduce your problem. But I'm very interested in knowing the cause of it if you or anyone else figures it out. In particular I'd like to know if it's a VM issue or an image issue (or both).
Dave
On Tue, Jan 31, 2012 at 11:26:57AM -0500, Jon Hylands wrote:
Actually, some additional information...
Turns out the 4.2 testing I was doing was with the Cog VM. With the normal 4.2 VM (which is the same as the 4.3 VM), the problem shows up in 4.2 also.
So this appears to be an issue with the latest Windows VM, which is Squeak4.1.1 from Jul 27, 2010...
- Jon
On Tue, Jan 31, 2012 at 11:12 AM, Jon Hylands jon@huv.com wrote:
Hi everyone,
I've ported some of my code into Squeak 4.3 (was running in 4.2 before), and ran into a weird issue comparing Date objects.
When you execute "Date today", it produces a Date object with DateAndTime localTimeZone's offset, which is set upon image startup to be Locale >> offsetLocalToUTC, which in turn calls Locale >> primTimezone.
On a 4.2 image, on both my XP and Windows 7 machines, that primitive returns -300 (minutes), which is -5 hours, which is correct (since I live in SW Ontario, Canada, which is EST).
On a 4.3 image, with or without updates, that method returns -240, which is -4, which is clearly wrong at this point in time.
- Jon
squeak-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
David T. Lewis -
Jon Hylands