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: Thu, 21 Mar 2002 10:36:00 -0000	[thread overview]
Message-ID: <20020321183601.4082.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: Thu, 21 Mar 2002 18:31:05 +0000

 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.


             reply	other threads:[~2002-03-21 18:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21 10: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 11:36 Neil Booth
2002-03-22  1:56 Mario Deilmann
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=20020321183601.4082.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: link
Be 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).