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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,10c4b1e7e98e6a93 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-05-17 02:57:26 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: dewar@gnat.com (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: Problems with Ada.Real_Time on GNAT? Date: 17 May 2002 02:57:26 -0700 Organization: http://groups.google.com/ Message-ID: <5ee5b646.0205170157.27179a3f@posting.google.com> References: <28d8936a.0205161133.3c9064b7@posting.google.com> <87k7q3c0di.fsf@deneb.enyo.de> <873cwr45xy.fsf@deneb.enyo.de> NNTP-Posting-Host: 205.232.38.244 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1021629446 16419 127.0.0.1 (17 May 2002 09:57:26 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 17 May 2002 09:57:26 GMT Xref: archiver1.google.com comp.lang.ada:24259 Date: 2002-05-17T09:57:26+00:00 List-Id: Florian Weimer wrote in message news:<873cwr45xy.fsf@deneb.enyo.de>... > Why do you think this is necessary? It's certainly unneeded if you > want to use just the timing facilities from Ada.Real_Time. That's good advice, indeed there is no requirement to run in root or anything else to use the facilities needed by this program. And there is no need to use FSU threads for this program. > (It's true that the FSU threads run-time library implements more > requirements of the real-time annex at the moment, but you'll never > reach full conformance on top of ordinary Linux anyway.) That's false, GNAT is fully compliant with all requirements of Annex D when running on any GNU/Linux version using FSU threads. Please don't make casual claims of non-compliance unless you have very specific knowledge of a non-compliant case (in which case please report the bug :-)