This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: non-ambiguous typedefs


Howard Hinnant <hhinnant@apple.com> writes:

| Hi All,
| 
| I'm wondering if the following behavior is:
| 
| 1.  An already reported bug.
| 2.  Not reported, I need to file a bugzilla.
| 3.  Disputed.
| 
| Here's the test case:
| 
| typedef unsigned short ushort;
| 
| namespace X
| {
|      typedef unsigned short ushort;
| }
| 
| using namespace X;
| 
| int main()
| {
|      ushort us = 0;
| }
| 
| We currently get:
| 
| error: 'ushort' was not declared in this scope

Plain compiler bug.  I'm not aware of any existing report to that
effect, though GCC/g++ currently is completely confused when it sees
apparently ambiguous declarations, and would report non-existent
declaration.  That needs fixing.

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]