Brent Pinkney said:
> Hi,
> 
> I have to reject Avi's changeset accurateDateAndTimeNowV2-avi 
> as it does 
> not pass the SUnit tests in the image.
> 
> ScheduleTest>>#testMonotonicity
> TimespanTest>>#testCurrent
> 
> A big part of the Chronology package was that DateAndTime instances 
> increase monotnoically - i.e
> 
> 	(DateAndTime now) = (DateAndTime now)	=> false.
> 
> This change set breaks that invariant.

I thought monotonicity meant that (DateAndTime now) >= (DateAndTime now)
would always be true. In other words, "DateAndTime now" considered as
a function would always be non-decreasing.

As Avi points out elsewhere, if you evaluate "DateAndTime now" faster
than the resolution of the clock, you should get the same value.

frank