Delay>>hasExpired et al.

Andy, Blair,

Thanks in large part to you and Dolphin, I appear to have software that is
sufficiently stable that I reboot only when Microsoft forces me via updates.
Can you confirm that system clock wraps are not handled?  Any speculation on
when they might be?

BTW, I recognize that a hurried attempt to fix the problem is _not_ in any
one's interest.  If need be, I suppose I can force myself to reboot [*]
machines every month :)

Have a good one,

Bill

[*] I will note that the rebooting would be a DLL of a lot less trouble if
Microsoft would respect the /noserialmice pre-boot flag, but that's another
story.

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

"Bill Schwab" <[hidden email]> wrote in message
news:[hidden email]...
> Andy, Blair,
>
> Thanks in large part to you and Dolphin, I appear to have software that is
> sufficiently stable that I reboot only when Microsoft forces me via
> updates.
> Can you confirm that system clock wraps are not handled?  Any speculation
> on
> when they might be?
>

The wrapping of the millisecond clock is ignored. No plans to fix at
present, although I will add a defect report for it. Off the top of my head
I would say that it will probably require no changes in the VM, just some
additional conditions in the Delay class. Since it only happens once every
40 to 50 days (if I remember correctly), it might need a little refactoring
to make it testable (so that the millisecond clock source can be
substituted).

Regards

Blair