Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site brl-vgr.ARPA
Path: utzoo!watmath!clyde!floyd!harpo!seismo!brl-vgr!gwyn
From: gwyn@brl-vgr.ARPA (Doug Gwyn )
Newsgroups: net.unix
Subject: Re: Improving C
Message-ID: <2836@brl-vgr.ARPA>
Date: Sat, 24-Mar-84 18:17:58 EST
Article-I.D.: brl-vgr.2836
Posted: Sat Mar 24 18:17:58 1984
Date-Received: Sun, 25-Mar-84 19:27:43 EST
References: <17422@sri-arpa.UUCP> <920@dartvax.UUCP>, <247@astrovax.UUCP>
Organization: Ballistics Research Lab
Lines: 11

Another point is that correct code benefits NOT AT ALL from run-time
subcript range checking and other such aids.  How about getting the
code right in the first place instead of relying on run-time detection
of errors to find your mistakes.  (This assumes you are able to
run an exhaustive set of test cases through your code anyway, which is
a very poor assumption.)  I recommend Myers' "The Art of Software
Testing" to those who care about the subject.

Input validation is a well-known requirement.  Good COBOL programmers
do this automatically.  Is it possible that there are no good UNIX
programmers?  :-)