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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,cae92f92d6a1d4b1
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!feeder.news-service.com!newsfeed.straub-nv.de!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: BrianG <briang000@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Ada.Execution_Time
Date: Thu, 16 Dec 2010 12:32:45 -0500
Organization: A noiseless patient Spider
Message-ID: <iedig0$ai2$1@news.eternal-september.org>
References: <ie1ih9$d02$1@news.eternal-september.org>
 <ie2v2k$aps$1@tornado.tornevall.net> <ie3gjn$oj$1@news.eternal-september.org>
 <4d05e737$0$6980$9b4e6d93@newsspool4.arcor-online.net>
 <ie91co$cko$1@news.eternal-september.org> <iebe2t$eua$1@munin.nbi.dk>
 <iebp66$4tl$1@news.eternal-september.org>
 <x4GdnbBBlM_CkpfQRVn_vwA@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 16 Dec 2010 17:32:48 +0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="BssHc7ONlcOOcC5Vapr56Q";
	logging-data="10818"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18GP/gUdADU1uISh7BrcHPE"
User-Agent: Thunderbird 2.0.0.24 (X11/20100623)
In-Reply-To: <x4GdnbBBlM_CkpfQRVn_vwA@giganews.com>
Cancel-Lock: sha1:6xx+7fsr+rLtgwojbam3Vc+L/2I=
Xref: g2news1.google.com comp.lang.ada:15985
Date: 2010-12-16T12:32:45-05:00
List-Id: <comp.lang.ada>

Peter C. Chapin wrote:
> On 2010-12-15 20:14, BrianG wrote:
> 
>> Then the package is misnamed too - How is "Execution_Time" not a time?
>> Wouldn't tying it explicitly to Real_Time imply some relation to "real
>> time" (whether that makes sense or not)?  Using Duration could help
>> that, since it's implementation-defined.
> 
> To me "execution time" sounds like a measure of how long a program has
> run (in some sense). In other words it sounds like some kind of time
> interval. "The execution time of this process was 10.102 seconds."
"CPU_Time" makes it more clear - it's not the execution time of the 
program, but the amount of CPU it has used.  If there's time-sharing, it 
can be less than the elapsed time used.  Or if there's multiple cores, 
it may be greater (although that may be unlikely as the task level).
> 
> However, people often use "time" to refer to some sort of absolute
> clock. "What time is it? It is now 8:07am on 2010-12-16." The basic
> confusion is that the term "time" is extremely ambiguous in ordinary
> usage. Not only is it used both for time intervals and absolute time
> values, but there are several different kinds of time one might talk about.
> 
> Peter