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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e7ac0b21c6d808e6
X-Google-Attributes: gid103376,public
From: tmoran@bix.com (Tom Moran)
Subject: Re: Timing of ADA code
Date: 1998/08/01
Message-ID: <35c3a56f.18740451@SantaClara01.news.InterNex.Net>#1/1
X-Deja-AN: 377082553
References: <35c12689.217545056@news.gatech.edu>
 <6psg15$a56$1@nnrp1.dejanews.com> <35c1cf02.40761361@news.gatech.edu>
 <6pssib$r9c$1@nnrp1.dejanews.com> <35c23701.67387591@news.gatech.edu>
 <Ex04Bp.55@jvdsys.nextjk.stuyts.nl> <35c37492.148697454@news.gatech.edu>
Organization: InterNex Information Services 1-800-595-3333
Newsgroups: comp.lang.ada
Date: 1998-08-01T00:00:00+00:00
List-Id: <comp.lang.ada>

>Calendar but if I understand the interface it appears
>that I can only get a accuracy to seconds
That depends on the run time system your compiler vendor supplies.
Are you sure that Ada.Calendar.Clock only ticks once/second?  Once
every 55 milliseconds is what Win95 supplies so a vendor would almost
have to work to throw away accuracy.  Note that Day_Duration is a
fixed point type with a delta probably (much) less than 1.0 seconds.
But even if it is in seconds, can't you just time 100 iterations of
the thing you want to time, then divide the elapsed time by 100?