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=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,61d8daec8bfa486e
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news4.google.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!85.158.31.10.MISMATCH!newsfeed-0.progon.net!progon.net!news-zh.switch.ch!switch.ch!news.belwue.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: An Example for Ada.Execution_Time
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: <ifaloj$j2e$1@news.ett.com.ua>
 <ifbi5c$rqt$1@news.eternal-september.org> <ife8r9$9m6$1@munin.nbi.dk>
 <ifj5u9$rr5$1@news.eternal-september.org>
Date: Fri, 31 Dec 2010 10:11:51 +0100
Message-ID: <1fb06tjt2dy1y$.1tkafcv9oya2w.dlg@40tude.net>
NNTP-Posting-Date: 31 Dec 2010 10:11:48 CET
NNTP-Posting-Host: 48232abc.newsspool4.arcor-online.net
X-Trace: 
 DXC=224T=foSDe8NTD<CL>55K=4IUK<Cl32<14Fo<]lROoR18kF<OcfhCO;72S`E2=fYY<[6LHn;2LCV>[<mhadbfdU;<P5N5\iCdc>6^KglOnY274
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news2.google.com comp.lang.ada:17249
Date: 2010-12-31T10:11:48+01:00
List-Id: <comp.lang.ada>

On Thu, 30 Dec 2010 18:51:30 -0500, BrianG wrote:

> Since D.16 defines CPU_Time as if it were a numeric value, is it too 
> much to ask why a conversion to some form of numeric value wasn't 
> provided?

But time is not a number and was not defined as if it were. It is the time
differences which are numeric. RM D.14 defines differences of CPU_Time as
Time_Span. Time_Span is numeric.

I think this is the core of misunderstanding. The thing you have in mind is
"time interval since the task start according to the execution time clock."
It is not Ada.Execution_Time.Clock, it is:

   Ada.Execution_Time.Clock - CPU_Time_First

There is a direct correspondence between two, yet they are conceptually
different things.

Happy New Year,

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de