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,703c4f68db81387d X-Google-Thread: 115aec,703c4f68db81387d X-Google-Thread: f43e6,703c4f68db81387d X-Google-Thread: 108717,a7c8692cac750b5e X-Google-Attributes: gid103376,gid115aec,gidf43e6,gid108717,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail NNTP-Posting-Date: Mon, 14 Mar 2005 16:12:58 -0600 From: "Randy Brukardt" Newsgroups: comp.lang.ada,comp.realtime,comp.software-eng,comp.programming References: <4229bad9$0$1019$afc38c87@news.optusnet.com.au> <1110052142.832650@athnrd02> <1110284070.410136.205090@o13g2000cwo.googlegroups.com> <395uqaF5rhu2mU1@individual.net> <112rs0bdr2aftdf@corp.supernews.com> <1inxxr988rxgg$.1w9dedak41k89.dlg@40tude.net> <112s1r0rf0o8nca@corp.supernews.com> <112sonip5v4dca6@corp.supernews.com> <112t3de6fu04f38@corp.supernews.com> <1110396477.596174.285520@o13g2000cwo.googlegroups.com> <112vb2t8eonuhed@corp.supernews.com> <1110422108.925127.54110@o13g2000cwo.googlegroups.com> <11329cb96h2p19f@corp.supernews.com> <113394jjvppao64@corp.supernews.com> <1133s3qnmqmbjfb@corp.supernews.com> <4232a9f7$0$26552$9b4e6d93@newsread4.arcor-online.net> <11369p5jrcc6835@corp.supernews.com> <1136h6a12qv8282@corp.supernews.com> Subject: Re: 10 rules for benchmarking (was Re: Teaching new tricks to an old dog (C++ -->Ada)) Date: Mon, 14 Mar 2005 16:15:20 -0600 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4927.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 Message-ID: NNTP-Posting-Host: 64.32.209.38 X-Trace: sv3-xJWKtsh2lpfCC8rFobPKwtFC3N9fxPiBD2tdEDP6q5WUMPawmcqKoLaY+4m8XghOYZEV07m4LaETW/5!RtvM9CpS2CyhJJqVBz92Gc/lBmpoCqHsFyXbQZUEjkGDr3KgnnTNLP5qDYEaS6wfoL+IKm6c94w6 X-Complaints-To: abuse@megapath.net X-DMCA-Complaints-To: abuse@megapath.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.31 Xref: g2news1.google.com comp.lang.ada:9401 comp.realtime:1482 comp.software-eng:5048 comp.programming:17950 Date: 2005-03-14T16:15:20-06:00 List-Id: CTips wrote: > BTW: I was looking around - I couldn't find an Ada equivalent to the > ISO C clock() routine. What is it? I can't believe that the Ada > standard community would have been *that* oblivious to performance > that they wouldn't put a performance measuring routine in the core > specification. As previously mentioned, it will be added to Ada 2005 (expected approval this summer). I believe that the reason that it didn't exist in previous versions of Ada was that directly targeting bare machines was an intended implementation of Ada. That is, the Ada RTS would provide the entire RTOS for the target, including tasking, exceptions, and so on. In that case, providing a CPU time function would have added overhead that may not have had any value to the user (you would have to keep track of it on every task switch whether it was used or not). Similarly, a lot of systems didn't provide anything like that. For instance, there wouldn't have been any portable way to do it on our MS-DOS compilers, and we had a policy of not depending on the hardware configuration (because that changed too frequently for us to keep up - we didn't want to be selling products that only worked on real IBM PCs and a few clones). Now, most Ada compilers target RTOSes rather than bare hardware boards, and most OSes of any sort include performance info, so it makes more sense to include it in the Standard. Randy Brukardt