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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,8a4455177648cb9e
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Idea: Array Boundary Checks on Write Access Only
Date: 1998/06/20
Message-ID: <dewar.898364494@merv>#1/1
X-Deja-AN: 364518242
References: <35851B64.5BF271C4@cl.cam.ac.uk> <35858FBC.4E5E@praxis-cs.co.uk>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 898364550 22787 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-06-20T00:00:00+00:00
List-Id: <comp.lang.ada>


It seems odd to have *any* runtime checks that can raise exceptions in
safety critical progams. Such programs are not supposed to have errors
that could write arrays out of bounds, and the certification and validation
process should be able to prove the absence of such errors.