Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site utastro.UUCP Path: utzoo!watmath!clyde!floyd!harpo!seismo!ut-sally!utastro!nather From: nather@utastro.UUCP (Ed Nather) Newsgroups: net.unix Subject: Re: Improving C Message-ID: <44@utastro.UUCP> Date: Thu, 15-Mar-84 18:29:03 EST Article-I.D.: utastro.44 Posted: Thu Mar 15 18:29:03 1984 Date-Received: Sat, 17-Mar-84 02:43:49 EST References: <17422@sri-arpa.UUCP> Organization: UTexas Astronomy Dept., Austin, Texas Lines: 21 [] From: Travis Lee WinfreyI 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.... Travis ------- If I may paraphrase a point made in "Software Tools" by K & P (I can't find the exact wording): This is much like wearing a parachute while you are in pilot's training on the ground, then discarding it when you go aloft. If the checking is needed for debugging, it is almost certainly needed for what is sometimes called "malicious input." -- Ed Nather ihnp4!{ut-sally,kpno}!utastro!nather Astronomy Dept., U. of Texas, Austin