While 68 years does seem a stretch, who in their right mind wants to code implicit time-bombs into their stuff? A vendor wants to be able to say "I'm game if you are." (I.e., totally NOT a microsoft mentality! Which is to say, reboot every few days else it stops working right.)
Handling monobased timer overflow is well understood, and has been since computing was invented. If the difference looks negative (a physical impossibility, so any such is an arithmetical artifact) you just flip it around and proceed with the (correct) positive difference. The only time this breaks down is if the true timeout interval approaches the wraparound time. Very few bits of code will try to schedule a non-calendrical event 68 years into the future! -- Jim _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
