Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site unc.UUCP Path: utzoo!watmath!clyde!akgua!mcnc!unc!tim From: tim@unc.UUCP (Tim Maroney) Newsgroups: net.unix Subject: Re: Improving C Message-ID: <6931@unc.UUCP> Date: Sat, 17-Mar-84 14:29:39 EST Article-I.D.: unc.6931 Posted: Sat Mar 17 14:29:39 1984 Date-Received: Sun, 18-Mar-84 08:21:45 EST References: <44@utastro.UUCP> Organization: CS Dept., U. of N. Carolina at Chapel Hill Lines: 14 I disagree that it is a mistake to remove array bounds checking and such after debugging is complete. If you have run a program on general test data (including anomalous data) and never gotten the error, then you may fairly safely assume that the error will not happen on any input data. It would be a mistake to sacrifice run-time efficiency for a check on an impossible (or at least VERY improbable) error. Of course, you'd better make sure that your test data really is "general". -- Tim Maroney, The Censored Hacker mcnc!unc!tim (USENET), tim.unc@csnet-relay (ARPA) All opinions expressed herein are completely my own, so don't go assuming that anyone else at UNC feels the same way.