Actually, some additional information...<div><br></div><div>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.</div><div><br>
</div><div>So this appears to be an issue with the latest Windows VM, which is Squeak4.1.1 from Jul 27, 2010...</div><div><br></div><div>- Jon</div><div><br><br><div class="gmail_quote">On Tue, Jan 31, 2012 at 11:12 AM, Jon Hylands <span dir="ltr"><<a href="mailto:jon@huv.com">jon@huv.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><div>Hi everyone,</div><div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>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).</div><div><br></div>
<div>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.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>- Jon</div><div><br></div>
</font></span></blockquote></div><br></div>