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

[Neil Booth <neil@daikokuya.demon.co.uk>]

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

From: Neil Booth <neil@daikokuya.demon.co.uk>
To: mdeil@pallas.de
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: Tue, 19 Mar 2002 19:48:40 +0000

 mdeil@pallas.de wrote:-
 
 > I found some strange behaviour with some of the g++ versions greater than 2.91 on different platforms with a small C++ code (included)
 > I investigated a little more and found out that in my opinion the program was badly coded. The header files included each others and also some of the system headers. So I cleaned up all headers so that there are no more
 > includes in the header files. Collected the used system and program header's and added the std namespace. Wow, what a suprise now all gcc versions include 3.0 accepts the code. 
 > 
 > Can you give me some insight's what makes this program so PRBLEMATIC are this ANSI/ISO feature problems ? All compilers that produce errors find them in their own include files which confuses me. I thought that the problems should be located in the original source code. 
 
 We cannot debug this easily for you.  However, you can probably get a deeper
 understanding of what is happening with the -H option.  Please compare
 the output of gcc -E -H yourfile.c between the two compilers, and see
 where they diverge.  It generates an include stack trace.
 
 Let us know if we can close this PR.
 
 Neil.