Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!sdcsvax!bruss
From: bruss@sdcsvax.UCSD.EDU (Brian Russ)
Newsgroups: net.lang.c,net.lang.c++
Subject: Re: Why are typedef names in the same name space as variable names?
Message-ID: <2183@sdcsvax.UCSD.EDU>
Date: Sat, 1-Nov-86 21:26:47 EST
Article-I.D.: sdcsvax.2183
Posted: Sat Nov  1 21:26:47 1986
Date-Received: Mon, 3-Nov-86 22:30:19 EST
References: <4220@ut-ngp.UUCP>
Reply-To: bruss@sdcsvax.UUCP (Brian Russ)
Organization: U.C. San Diego
Lines: 25
Keywords: typedef variable name space
Xref: mnetor net.lang.c:6256 net.lang.c++:402

In article <4220@ut-ngp.UUCP> dlnash@ut-ngp.UUCP (Donald L. Nash) writes:
>Why are typedef names in the same name space as variable names? ... 
> ...  This means that you cannot have
>something like:
>
>	struct foo { /* ... */ };
>
>	int foo;
>
>in C++.
>

	If they weren't in the same name space, you could, in addition
to the above, write:

	struct foo { /* ... */ };

	foo foo;

	Yuch!  Do you really want/need this flexibility?  In my opinion,
it's better the way it is now.