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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: "Jeffrey R. Carter" Newsgroups: comp.lang.ada Subject: Re: Ada.Strings.Fixed.Count raises Storage_Error Date: Wed, 29 Jun 2016 12:40:17 -0700 Organization: Also freenews.netfront.net; news.tornevall.net; news.eternal-september.org Message-ID: References: <57346ac8$0$4570$426a74cc@news.free.fr> <57707888$0$5274$426a34cc@news.free.fr> <43a09f40-fdea-461e-9b0a-4419b86c1a56@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 29 Jun 2016 19:40:20 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="48b46be33beed75863f69afa437f956b"; logging-data="13689"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1//f2xa0I8+xOGzPmE1qtfRlcptDjZPNhI=" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 In-Reply-To: Cancel-Lock: sha1:TNkaWc1DbXe9mymv9gqUMTRAkew= X-Enigmail-Draft-Status: N1110 Xref: news.eternal-september.org comp.lang.ada:30973 Date: 2016-06-29T12:40:17-07:00 List-Id: On 06/29/2016 11:49 AM, Niklas Holsti wrote: > > I'm astonished that you seem to be saying that Gödel's results mean that this > clear and simple bug in a library function should not be reported to AdaCore. > Really. Perhaps you are afraid that this is the last bug in GNAT, and as you > believe that every compiler must have at least one bug, removing this bug would > mean that GNAT would no longer be a compiler :-) This is not an error in the compiler; it's an error in a general-purpose library. Fixing it will not change the number of errors in the compiler. We're told that the ARG has decided that some corner cases are too difficult for compiler writers to get right, so the ARG won't require that they be handled correctly. The argument that this permission means the function in question doesn't need to be correct is wrong because the error in question isn't something the compiler has difficulty compiling. It's an error by the implementor of the subprogram that the compiler compiles correctly. The argument that correcting the error would have a negative effect on the performance of the subprogram, and that it's more important that it be fast than that it be correct is wrong because correctness is always more important than performance for a general-purpose library. It's expected that a general-purpose library's performance may not be acceptable for some applications. Such applications know that a general-purpose library may not meet their performance needs. -- Jeff Carter "What's the amount of the insult?" Never Give a Sucker an Even Break 104