Dec. 29, 2012
9:51 p.m.
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