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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f039470e8f537101 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-07-23 18:42:33 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!in.100proofnews.com!in.100proofnews.com!cycny01.gnilink.net!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny02.gnilink.net.POSTED!53ab2750!not-for-mail From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030708 Thunderbird/0.1a X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ariane5 FAQ References: <1058799152.775376@master.nyc.kbcfp.com> <1058810510.375902@master.nyc.kbcfp.com> <1058813341.841940@master.nyc.kbcfp.com> <1058816605.566685@master.nyc.kbcfp.com> <1058969472.350716@master.nyc.kbcfp.com> <1058982513.114816@master.nyc.kbcfp.com> <3F1ED712.2070405@attbi.com> <1058991539.971642@master.nyc.kbcfp.com> <3F1F12FB.2060901@attbi.com> In-Reply-To: <3F1F12FB.2060901@attbi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Date: Thu, 24 Jul 2003 01:42:32 GMT NNTP-Posting-Host: 162.83.157.195 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny02.gnilink.net 1059010952 162.83.157.195 (Wed, 23 Jul 2003 21:42:32 EDT) NNTP-Posting-Date: Wed, 23 Jul 2003 21:42:32 EDT Xref: archiver1.google.com comp.lang.ada:40741 Date: 2003-07-24T01:42:32+00:00 List-Id: Robert I. Eachus wrote: > It was if you see this value something is bad wrong, > and maybe it can be figured out from a data dump. But the Ariane 4 code was not written such that a value exceeding the assumed Ariane 4 range would cause such a dump. The code was written to assume that the value would not be exceeded, and to let the code do whatever it might if the value was exceeded. A value between the spec max and the overflow min would (probably) not have caused such a dump. The code did "what it was designed to do" only on an Ariane 4. On the Ariane 5, it did not do "what it was designed to do" because the design did not cover out of range values. If the design had covered such values, it would not have specified one behavior for small large values and a different behavior for large large values.