Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site dartvax.UUCP Path: utzoo!watmath!clyde!floyd!harpo!seismo!hao!hplabs!tektronix!decvax!dartvax!andyb From: andyb@dartvax.UUCP (Andy Behrens) Newsgroups: net.unix Subject: Re: Improving C Message-ID: <920@dartvax.UUCP> Date: Mon, 19-Mar-84 21:40:45 EST Article-I.D.: dartvax.920 Posted: Mon Mar 19 21:40:45 1984 Date-Received: Wed, 21-Mar-84 08:36:20 EST References: <17422@sri-arpa.UUCP> Organization: Dartmouth College Lines: 14 > I personally would kill for built-in type checking and array > bounds checking during the debugging phase of my programs. They could be > removed after the program reached production quality.... Dijkstra points out that it is foolish to just use bounds checking during testing (when you can recover from errors), only to remove the checking for production runs (when an error becomes a serious thing). -- Andy Behrens P.O. Box 24, East Thetford, Vermont UUCP: {decvax,linus,cornell,dalcs}!dartvax!andyb CSNET: andyb@dartmouth ARPA: andyb%dartmouth@csnet-relay