Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ncar!boulder!grunwald
From: grunwald@foobar.colorado.edu (Dirk Grunwald)
Newsgroups: comp.sys.mips
Subject: Re: cc bug?
Message-ID: <23420@boulder.Colorado.EDU>
Date: 12 Jul 90 19:35:46 GMT
References: <2742@uakari.primate.wisc.edu>
Sender: news@boulder.Colorado.EDU
Reply-To: grunwald@foobar.colorado.edu
Organization: University of Colorado at Boulder
Lines: 25
In-reply-to: bin@primate.wisc.edu's message of 12 Jul 90 18:36:43 GMT


> RISC/os 4.01
> cc 2.0
> 
> # include	<stdio.h>
> 
> main ()
> {
> char	*str;
> 
> 	fprintf (stderr, "why does this compile?\n"< str);
> }
---

	this is roughly:

	char *foo = "why does this compile?\n";
	char *str;
	int condition = foo < str;
	fprintf(stderr, condition);


and the value of condition would be either 0 or 1. Probably 0. When
fprintf attempt to print the null and/or garbage string living at
address 0 or 1, it barfs.