Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!husc6!bbn!apple!sun!aeras!elxsi!beatnix!corbett
From: corbett@beatnix.UUCP (Bob Corbett)
Newsgroups: comp.std.c
Subject: Re: Multiple typedefs
Keywords: typedefs, includes, defines
Message-ID: <2636@elxsi.UUCP>
Date: 5 May 89 20:55:18 GMT
References: <2322@lethe.UUCP> <10167@smoke.BRL.MIL> <2402@lethe.UUCP> <10190@smoke.BRL.MIL> <12955@haddock.ima.isc.com>
Sender: news@elxsi.UUCP
Reply-To: uunet!elxsi!corbett (Bob Corbett)
Organization: ELXSI, Inc.
Lines: 19

In article <12955@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes:
!It seems to me that the compiler is going to have to be able to handle such a
!case anyway.  Note that
!	typedef int foo;
!	void f(void) {
!	    typedef int foo;
!	}
!*is* legal (and would be even if the two types didn't match; the second simply
!hides the first until end-of-scope).

The latest draft of the standard I have (December 7, 1988) does not allow a
storage-class-specifier (in this case typedef) in a struct-declaration-list.
If X3J11 added this feature since that draft, we need another round of public
review.

!Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint

					    Faithfully yours,
					    Bob Corbett