Re: c++/6001: g++ problems with nested headers from > egcs-2.91.66 until 3.0.0

[Mario Deilmann <Mario.Deilmann@pallas.com>]

The following reply was made to PR c++/6001; it has been noted by GNATS.

From: Mario Deilmann <Mario.Deilmann@pallas.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/6001: g++ problems with nested headers from > egcs-2.91.66 until 3.0.0
Date: Fri, 22 Mar 2002 10:46:04 +0100 (MET)

 Hi Neil,
 
 just received your email:
 
 > Almost certainly not a compiler bug, but user error of some subtle kind
 > (agreed with submitter).
 
 I agreed to close the bug report because I found a workaround but in my
 opinion it's not a "user error" :o. 
 
 >I _am_ sure the compiler is not at fault, so
 
 If I include nested heades and system headers and that causes parse errors
 in the SYSTEM headers of the Compiler this is by no means a user error !
 So why can you be sure it's not a compiler error ? 
 
 The programm seems syntactically correct (it compiles with no errors on
 different platforms with different compilers).
 
 >I'll close the PR.
 
 Anyhow close this thing, have a nice day ;).
 
 Viele Gruesse / Best Regards
 
 -- Mario 
 
 Mario Deilmann
 Senior Sales Engineer
 --------------------------------------------------------------------
 //// pallas 
 Pallas GmbH / Hermuelheimer Str. 10 / 50321 Bruehl / Germany
 Mario.Deilmann@pallas.com / www.pallas.com
 Tel +49-2232-1896-31 / Fax +49-2232-1896-29
 --------------------------------------------------------------------
 
 On Thu, 21 Mar 2002, Neil Booth wrote:
 
 > Mario Deilmann wrote:-
 > 
 > > again thanks for your help. The hint was very helpful to get the right
 > > output but I cannot see why I got an error like
 > > 
 > > /home/mdeil/bin/../include/g++-v3/sparc-sun-solaris2.7/bits/basic_file_model.h:39:
 > > parse error before `;' token
 > > 
 > > only because I changed the sequence of some includes. The code with the
 > 
 > OK, thanks.  The error is something subtle with the effects of changing
 > the include order.  Maybe some headers don't have guards and are being
 > included twice.  However, I _am_ sure the compiler is not at fault, so
 > I'll close the PR.
 > 
 > Neil.
 >