From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: *
X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_20,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!WINNIE.FIT.EDU!saharbaugh%roo.dnet
From: saharbaugh%roo.dnet@WINNIE.FIT.EDU
Newsgroups: comp.lang.ada
Subject: Package Calendar
Message-ID: <9007051846.AA01362@winnie.fit.edu>
Date: 5 Jul 90 18:46:50 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
List-Id: <comp.lang.ada>

Here are a few other things to consider about package Calendar:
1. There are two values for midnight (0.0 & 86400.0) like
   a magnetic compass which has two values for north ( 0.0 & 360.0) but
   unlike my wall clock where straight up is 12:00 not 0:00.
2. There is no provision in package Calendar for indicating
   that the reported value is suspect.  My >50 year old mantle
clock has a flag that drops when the power fails to indicate
that you should suspecct what the face is saying( good
thing my face has no such flag). My digital clocks flash when
power failure destroys their credibility.  
3.  There is no provision for setting the clock or handling
    leap seconds, when the committee in France adds a second to
    adjust for slowing of the earth's rotational rate.
-
   People tell me I am nitpicking to which I say "Oh!, If you
don't really want to know what time it is then use
package Calendar, it is useful for short duration
benchmarks etc. BUT if you are building a real-time control
system then (as the posting said)roll-your-own",  I see
advertized boards for the PC which decode WWVB time
signals. I believe you must turn to an integrated hardware/software
solution for serious timekeeping.
regards, sam harbaugh
---------------------