Dec. 29, 2012
10:54 p.m.
midnight should be local time and DateAndTime work internally with UTC time only so yes this is wrong :), #seconds should be 0 and only the timezone has "special" values. On 2012-12-29, at 18:51, Max Leske <maxleske@gmail.com> wrote:
Possible bug in 2.0 which messes with equality checks:
"DateAndTime midnight" will answer a DateAndTime with seconds set to the UTC seconds. In my case (UTC +1) that's -3600 seconds. I'm pretty sure that seconds should be 0. This messes up equality checks for Date because Date class>>current uses #midnight.
Please confirm and I'll open a bug report.
Cheers, Max