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,5b15c37c5d0c986f X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!postnews.google.com!e56g2000cwe.googlegroups.com!not-for-mail From: "Anh Vo" Newsgroups: comp.lang.ada Subject: Re: Designing Timers using Ada.Real_Time.Timing_Events package Date: 27 Mar 2006 16:07:01 -0800 Organization: http://groups.google.com Message-ID: <1143504421.717575.141290@e56g2000cwe.googlegroups.com> References: <1143351567.528574.297850@z34g2000cwc.googlegroups.com> <1fiau0e4pe84o$.gulfgysczk5i$.dlg@40tude.net> <1143389936.844624.243020@i40g2000cwc.googlegroups.com> <1143402228.182836.29570@v46g2000cwv.googlegroups.com> <3itd22hcekts5lsojdqjnn966bbvc8fckh@4ax.com> <1143417218.070618.302820@i39g2000cwa.googlegroups.com> <0mae22lshe5nee8pt8h7seussloebv07g3@4ax.com> <1143435673.255301.186540@u72g2000cwu.googlegroups.com> <5vse22h4mc1och27s0nkbv986csi2rorki@4ax.com> NNTP-Posting-Host: 209.225.224.226 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1143504427 31772 127.0.0.1 (28 Mar 2006 00:07:07 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 28 Mar 2006 00:07:07 +0000 (UTC) In-Reply-To: <5vse22h4mc1och27s0nkbv986csi2rorki@4ax.com> User-Agent: G2/0.2 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: e56g2000cwe.googlegroups.com; posting-host=209.225.224.226; posting-account=JVr7Xg0AAAAI3MbuARxMmvWLmA7qdJMx Xref: g2news1.google.com comp.lang.ada:3664 Date: 2006-03-27T16:07:01-08:00 List-Id: >> Yes, it is clearly a typo. However, it should be OK because Ada is a >> case insensitive language. > I used upper case to point out that the closing S was /missing/ in > your posted code... I expect some thing like this typo occur once in a while. > Given the supplied code I, at least, could not confirm that this is > true in all cases... And if you really intend for something more > flexible, you should be relying on the argument being passed in, not on > some static single entity in the background, to identify which timer > event triggered. I am afraid I do not understand what mean here. Argument passing does not always provide flexibility for all cases specially this one. > > No, it is for real since I compiled and run it. Otherwise, I would not > > Again, you misunderstood me... I meant that /my conclusions/ were > hypothetical -- in that it is all based upon reading various web pages > and playing with code. I am puzzled here also. I do not see how the combination of my codes and your reading various web pages make you conclude that this is hypothetical. > As for building a GCC line... Sorry, but I am not configured to do > such; especially not on a home WinXP machine -- it it isn't available as > part of a pre-built binary installer, it doesn't go on.... At work, the > company has a support agreement with ACT, and is using GNAT 3.16a; they > are only now studying GNAT Pro for compatibility -- so obviously I > wouldn't have access to this timing module there either (even if they > converted to GNAT Pro). It shoud not be difficult to build gcc-4.2.0 if you have a linux box and approximately three hours. AV