public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@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 11:36:00 -0000 [thread overview] Message-ID: <20020322193602.12821.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6001; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.demon.co.uk> To: Mario Deilmann <Mario.Deilmann@pallas.com> 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 19:30:02 +0000 Mario Deilmann wrote:- > 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 ? Because it would be a preprocessor bug, and I'm sure there are no bugs in this area in CPP. > The programm seems syntactically correct (it compiles with no errors on > different platforms with different compilers). You should investigate what the issue is. Have you created preprocessed source and examined it? Have you created preprocessed source with a compiler that works and examined it? I bet there's a difference, and we need to know what is causing it. > Anyhow close this thing, have a nice day ;). Well, I don't want to close something that is a bug, but you have not convinced me it is a bug. I urge you to find out what exactly is odd about the preprocessed source, and *why* it is odd. Otherwise we'll never get anywhere - I can't replicate your system, only you can. Have you created the preprocessed source? Can you send it to me? Can you send me the preprocessed source from a compiler that works? Neil.
next reply other threads:[~2002-03-22 19:36 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-22 11:36 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-26 2:16 Mario Deilmann 2002-03-25 10:36 Neil Booth 2002-03-22 1:56 Mario Deilmann 2002-03-21 10:36 Neil Booth 2002-03-21 10:32 neil 2002-03-21 1:36 Mario Deilmann 2002-03-20 10:16 Neil Booth 2002-03-20 1:46 Mario Deilmann 2002-03-19 11:56 Neil Booth 2002-03-19 7:16 mdeil
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020322193602.12821.qmail@sources.redhat.com \ --to=neil@daikokuya.demon.co.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).