Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!decwrl!decvax!ima!mirror!frog!john
From: john@frog.UUCP (John Woods)
Newsgroups: comp.std.c
Subject: Re: Some Comments & Questions about ANSI C
Message-ID: <1521@frog.UUCP>
Date: 16 Jun 89 01:48:00 GMT
References: <GEOFF.89Jun11231924@onyx.cs.warwick.ac.uk> <13680@haddock.ima.isc.com>
Organization: Misanthropes-R-Us
Lines: 19

In article <13680@haddock.ima.isc.com>, karl@haddock.ima.isc.com (Karl Heuer) writes:
I> In article <GEOFF.89Jun11231924@onyx.cs.warwick.ac.uk> geoff@cs.warwick.ac.uk (Geoff Rimmer) writes:
 > >	One of these days, I'm going to write an ANSI C compiler.  And whenever
l> >	it encounters some code whose behavior is undefined (such as
i> >	fflush(stdin);) it will draw a picture of Snow White (tm) on the
k> >	screen, and then play Rule Brittania 3 times, before crashing with a
e> >	segmentation fault, and leaving a
 > >		while(1){fork();malloc(UINT_MAX);}
i> >	running in the background.
t>
.> Quality of Implementation issues are usually resolved by the free market.

Indeed they are.
Geoff, when you finish writing that compiler, I want TWO of them.
-- 
John Woods, Charles River Data Systems, Framingham MA, (508) 626-1101
...!decvax!frog!john, john@frog.UUCP, ...!mit-eddie!jfw, jfw@eddie.mit.edu
    People...How you gonna FIGURE 'em?
    Don't bother, S.L.--Just stand back and enjoy the EVOLUTIONARY PROCESS...