Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pur-ee.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!inuxc!pur-ee!ecn-ee!davy
From: davy@ecn-ee.UUCP
Newsgroups: net.unix
Subject: Re: Improving C - (nf)
Message-ID: <1661@pur-ee.UUCP>
Date: Mon, 5-Mar-84 21:21:36 EST
Article-I.D.: pur-ee.1661
Posted: Mon Mar  5 21:21:36 1984
Date-Received: Tue, 6-Mar-84 06:57:01 EST
Sender: notes@pur-ee.UUCP
Organization: Electrical Engineering Department , Purdue University
Lines: 21

#R:sri-arpa:-1688400:ecn-ee:17100003:000:641
ecn-ee!davy    Mar  5 09:08:00 1984


I would like to clarify my previous posting on "Improving C" -- 

	I didn't mean to say that I thought run-time checks were lousy
as a rule.  As a matter of fact, I'm all for them.  My point was that
this stuff DOES NOT belong in the language, it belongs in the compiler.
I would love to have a C compiler with a flag to turn on array bounds
checking (ala the f77 compiler), and other neato debugging stuff.  But
I don't think it should be part of the language, as it is with Pascal.

Thanks for everyone's comments so far, but please, don't flame at me
for this specific point any more.

--Dave Curry
decvax!pur-ee!davy
eevax.davy@purdue