Bug#168706: marked as done (g++-3.0: Bad syntax error on nested classes' member functions.)

2002-12-27 Thread Debian Bug Tracking System
Your message dated Fri, 27 Dec 2002 12:52:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bad syntax error on nested classes' member functions. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this

Bad syntax error on nested classes' member functions.

2002-11-16 Thread Martin v. Loewis
This is not a bug in the compiler, but in your code. Looking at the declaration foo_t a::b::frobnicate() { I notice that the scope of a::b is only reentered at the opening ( of the method declaration, thus "foo_t" is *not* found to be the typedef. Instead, it is treated as a plain identifier (o

Bug#168706: g++-3.0: Bad syntax error on nested classes' member functions.

2002-11-11 Thread Ian Turner
Package: g++-3.0 Version: 1:3.0.4-7 Severity: normal The source below makes G++-3.0 report a syntax error where none exists. Basically it doesn't wait before giving up on the typename. // Comment out to make it work. #define BREAK struct a { struct b { typedef unsigned int foo_t; foo_