<div class="gmail_quote">On Sat, Feb 4, 2012 at 12:43 AM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>></span> wrote:<br><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">I'm struggling to understand why "Date today" should be a TimeSpan that</div></div>
begins at some time other than midnight in my local time zone. The date<br>
that I think of as "4 February 2012" began about 20 minutes ago here in<br>
Detroit, but in London and Paris it is old news.<br></blockquote><div><br></div><div>David,</div><div><br></div><div>The issue that I'm having is this:</div><div><br></div><div>When I evaluate and store this object today: (Date newDay: 1 month: 1 year: 2012), and then six months later I evaluate exactly the same expression, because I live in a country where daylight savings is applied, those two objects will not be equal.</div>
<div><br></div><div>I can't think of a single logical reason why it should work that way. When I create a date (any date), it sets the timezone of the date to be whatever current timezone I happen to be in. That makes Date completely unusable as a historical indexing object.</div>
<div><br></div><div>- Jon</div><div><br></div></div>