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,8da181ade72859cf X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit From: Brian May Newsgroups: comp.lang.ada Subject: Re: timeouts References: <2jVUc.13319$Fg5.12445@attbi_s53> <2p63roFgloq0U1@uni-berlin.de> Date: Fri, 27 Aug 2004 08:59:18 +1000 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) Cancel-Lock: sha1:hkFWlMXrvmbh0478NEvAhsfValc= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: dsl-202-173-153-89.vic.westnet.com.au X-Trace: news.melbourne.pipenetworks.com 1093561157 202.173.153.89 (27 Aug 2004 08:59:17 +1000) X-Complaints-To: abuse@pipenetworks.com X-Abuse-Info: Please forward all headers to enable your complaint to be properly processed. Path: g2news1.google.com!news1.google.com!newsfeed.stanford.edu!nntp.cs.ubc.ca!newsfeeds.ihug.co.nz!ihug.co.nz!news.xtra.co.nz!news.mel.connect.com.au!duster.adelaide.on.net!news.melbourne.pipenetworks.com!not-for-mail Xref: g2news1.google.com comp.lang.ada:3058 Date: 2004-08-27T08:59:18+10:00 List-Id: >>>>> "Jano" == Jano writes: Jano> And I concur with some other poster: is too bad that the Jano> latest public release of gnat for windows carries two or Jano> three traps like this not mentioned in the users guide for Jano> NT. These are long-time known and fixed bugs, at least a Jano> link in the download page to some bugs page would be of Jano> interest (that's to say, if nobody at ACT is interested in Jano> or have the time to re-package 3.15p or make a new public Jano> release). If I had known about the bugs before hand, I would have taken some other approach to avoid the limitations or waited until the bug is fixed before porting the code over to Ada. Even if I developed the code, if the bugs were documented somewhere I could find, then I can verify it was a compiler bug and not a bug in my code. Normally, suspected compiler bugs are really hidden bugs in my code... As it is, I couldn't verify this until raising the issue on this newsgroup, and even here, I had to wait for firm verification (not that I am complaining). What other known traps exist? -- Brian May