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!linus!decvax!harpo!ihnp4!inuxc!pur-ee!iuvax!apratt
From: apratt@iuvax.UUCP
Newsgroups: net.lang
Subject: 'lint' and strong typing - (nf)
Message-ID: <1376@pur-ee.UUCP>
Date: Fri, 13-Jan-84 07:40:06 EST
Article-I.D.: pur-ee.1376
Posted: Fri Jan 13 07:40:06 1984
Date-Received: Sat, 14-Jan-84 03:28:57 EST
Sender: notes@pur-ee.UUCP
Organization: Electrical Engineering Department , Purdue University
Lines: 19

#N:iuvax:11800011:000:697
iuvax!apratt    Jan 12 21:06:00 1984

<:>

Into the strong-typing fray:
	Could somebody tell me why a pre-processor couldn't be used to flag
type conflicts, rather than writing them into the language?  "Lint" is the
obvious example, and, if you want to be stern, you could require that each
line of code which fails "lint" must be justified in writing, subject to
somebody's approval. If the application lends itself to type-mixing, you
should certainly be allowed to do it. An example: using (char *) in C to
point to an arbitrary object. Specifically with reference to the previous
note about the space program, frozen implementations mean never having to
say you're portable.
							-- Allan Pratt
					...ihnp4!inuxc!iuvax!apratt