Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: compile time type checking
Message-ID: <8193@mimsy.UUCP>
Date: Wed, 26-Aug-87 23:28:07 EDT
Article-I.D.: mimsy.8193
Posted: Wed Aug 26 23:28:07 1987
Date-Received: Sat, 29-Aug-87 05:59:18 EDT
References: <1065@vu-vlsi.UUCP> <2231@cbmvax.UUCP> <36@sarin.UUCP> <12962@amdahl.amdahl.com>
Distribution: na
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 25

In article <12962@amdahl.amdahl.com> chuck@amdahl.amdahl.com (Charles
Simmons) writes:
>Yes, lint does work quite well.  Unfortunately, I come from a PL1
>background where the compiler generated type-checking information
>and the linker made sure everything matched.  With lint, I have to
>have to perform an extra pass through my code.  Admittedly, it's not
>a whole lot of work, but if type-checking were integrated with the
>compiler, things would move along a little faster...

	% cat bin/cc
	: lint, then compile
	case $# in
	0) echo "usage: $0 [flags] [files]" 1>&2; exit 1;;
	esac
	lint -h "$@"
	/bin/cc "$@"

Well, this version is *too* simple, but you should get the idea.
You folks at Amdahl should not need to worry about compilation
speed! :-)  (Those are the kind of machines where you run `make'
and wonder why it just *printed* all the commands without running
them ... then you find out it *did* run them.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chthe