<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
> So the current behavior of two equal dates being considered not-equal is<br>
> as jarring as your counter example of two non-equal dates (different<br>
> timezone) being considered equal.<br></blockquote><div><br></div><div>Indeed!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
There doesn't seem to be an easy, direct solution because I'm assuming we<br>
don't have a primitive for "the offset at this location on X date in the<br>
past". So the next best thing might be a PlatonicDate (obviously a<br>
name-in-progress :)) that represents the abstract idea of a Date without<br>
regard to location, and then an object to connect a particular place/offset<br>
to that concept (but the second one would have the same problem as we<br>
currently have).<br></blockquote><div><br></div><div>Well, for me at least, the solution we chose for Squeak has been working well. Here's the main discussion:</div><div><br></div><div> <a href="http://lists.squeakfoundation.org/pipermail/squeak-dev/2012-February/162872.html">http://lists.squeakfoundation.org/pipermail/squeak-dev/2012-February/162872.html</a><br>
</div><div><br></div></div></div></div>