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.9 required=5.0 tests=BAYES_00 autolearn=ham
	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: 
 g2news2.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!news.in2p3.fr!in2p3.fr!news.ecp.fr!news.jacob-sparre.dk!pnx.dk!not-for-mail
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
Subject: Re: Ada.Execution_Time
Date: Mon, 20 Dec 2010 18:32:34 -0600
Organization: Jacob Sparre Andersen
Message-ID: <ieosj5$ebs$1@munin.nbi.dk>
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> <ief8ou$27ij$1@news.ett.com.ua>
 <iejsu9$lct$1@news.eternal-september.org>
 <op.vnxz4kmplzeukk@jellix.jlfencey.com>
NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net
X-Trace: munin.nbi.dk 1292891557 14716 69.95.181.76 (21 Dec 2010 00:32:37 GMT)
X-Complaints-To: news@jacob-sparre.dk
NNTP-Posting-Date: Tue, 21 Dec 2010 00:32:37 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Xref: g2news2.google.com comp.lang.ada:17057
Date: 2010-12-20T18:32:34-06:00
List-Id: <comp.lang.ada>

"Vinzent Hoefler" <0439279208b62c95f1880bf0f8776eeb@t-domaingrabbing.de> 
wrote in message news:op.vnxz4kmplzeukk@jellix.jlfencey.com...
...
> Yes, but so what? The intention of Ada.Execution_Time wasn't to provide 
> the
> user with means to instrument the software and to Text_IO some mostly
> meaningless values (any decent profiler can do that for you), but rather a
> way to implement user-defined schedulers based on actual CPU usage. You 
> may
> want to take a look at the child packages Timers and Group_Budget to see 
> the
> intended usage.

Probably, but I wanted to use Ada.Execution_Time to *write* a "decent 
profiler" for our Ada programs. Since Janus/Ada doesn't use the system 
tasking facilities (mostly for historical reasons), existing profilers don't 
do a good job if the program includes any tasks. I've used various hacks 
based on Windows facilities to do part of the job, but Ada.Execution_Time 
would provide better information (especially for tasks).

Similarly, anyone that wanted portable profiling information probably would 
prefer to use Ada.Execution_Time rather than to invent something new (and 
neecessarily not as portable). I found this sort of usage at least as 
compelling as the real-time usages.

                                       Randy.