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,56525db28240414a X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.201.129 with SMTP id ka1mr111267pbc.4.1343316902077; Thu, 26 Jul 2012 08:35:02 -0700 (PDT) Path: c10ni38192pbw.0!nntp.google.com!news1.google.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Martin Newsgroups: comp.lang.ada Subject: Re: Efficient Sequential Access to Arrays Date: Thu, 26 Jul 2012 08:18:35 -0700 (PDT) Organization: http://groups.google.com Message-ID: <5f618663-50d5-4f23-a5de-2ff3e6f6eb8e@googlegroups.com> References: <01983f1c-f842-4b1f-a180-bcef531dad4c@googlegroups.com> <87ipdf4vh6.fsf@mid.deneb.enyo.de> <4ce44d2d-d789-42a0-a6ed-035f7f8d58be@googlegroups.com> <32f60786-0236-4277-b936-f87b1cb8045b@t1g2000pbl.googlegroups.com> NNTP-Posting-Host: 20.133.0.8 Mime-Version: 1.0 X-Trace: posting.google.com 1343316901 11215 127.0.0.1 (26 Jul 2012 15:35:01 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 26 Jul 2012 15:35:01 +0000 (UTC) In-Reply-To: <32f60786-0236-4277-b936-f87b1cb8045b@t1g2000pbl.googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=20.133.0.8; posting-account=g4n69woAAACHKbpceNrvOhHWViIbdQ9G User-Agent: G2/1.0 Content-Type: text/plain; charset=ISO-8859-1 Date: 2012-07-26T08:18:35-07:00 List-Id: On Thursday, July 26, 2012 3:47:14 PM UTC+1, Robin Vowels wrote: [snip] > There's really no point in executing code without such checks. > You may never know that there is a bug in the code. But you could use other tools to prove that removal of such checks are safe - e.g. Polyspace. -- Martin