In message <[EMAIL PROTECTED]>, Rob Seaman writes:
>> 3) maximize scheduling horizon. > >That's one of the issues with leap hours - it's easy to maximize a >schedule, simply never do something. I believe this is really a >question of imposing a fixed schedule that happens to be of long >duration. Perhaps I misunderstood your point. This is the main objection to leapseconds as they are now: we get too short notice. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
