Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!rutgers!mcnc!uvaarpa!murdoch!opal.cs.Virginia.EDU!ecl2v
From: ecl2v@opal.cs.Virginia.EDU (Edmond C. Loyot)
Newsgroups: comp.lang.c++
Subject: Re: Local typedef possible?
Message-ID: <1991Jun22.182615.16885@murdoch.acc.Virginia.EDU>
Date: 22 Jun 91 18:26:15 GMT
Sender: usenet@murdoch.acc.Virginia.EDU
Reply-To: ecl2v@opal.cs.Virginia.EDU (Edmond C. Loyot)
Organization: University of Virginia
Lines: 18

The ARM says that what you want to do is legal.  Consider this example from
page 189 of the ARM:

class X {
	typedef int I;
	I a;
};

I b; // error

However when I run it through my 2.0 C++ compiler, it does not flag the error.
I think this is a throwback to the days of 1.2 when type names
(including classes) declared in a class where in the global scope.  This
is definately an
error, but was probably allowed for backward compatability (my 2.0 compiler is
based on the ATT 2.0 compiler).  I can't think of a work around.

Ed