Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!columbia!cucca!alan
From: alan@cucca.UUCP (Alan Crosswell)
Newsgroups: net.lang.c
Subject: unique namespace for typedefs, struct names, struct tags?
Message-ID: <183@cucca.UUCP>
Date: Wed, 12-Mar-86 11:15:49 EST
Article-I.D.: cucca.183
Posted: Wed Mar 12 11:15:49 1986
Date-Received: Sat, 15-Mar-86 18:27:28 EST
Organization: Columbia University Center for Computing Activities
Lines: 21

I recently ran into a problem with a C compiler with the following
typedef:

	typedef struct foo {
		struct foo *next;
		int foo;
	} foo;

It didn't like the multiple uses of "foo".  Since I am porting
someone else's large program and not writing one from scratch,
the solution of "don't do it that way" doesn't work for me.

Is there any statement in the ANSI proposed standard regarding this
name space issue?  I'd like to be able to coax my compiler vendor
to fix it with a reasonable argument like conformance rather than
saying "well,  it works right with the 4.2 compiler." 

Thanks in advance.

Alan Crosswell
Columbia University