From: "Tom Browder" <tom.browder@gmail.com>
To: "Eljay Love-Jensen" <eljay@adobe.com>
Cc: "David Arthur" <darthur@tantacomm.com>, GCC-help <gcc-help@gcc.gnu.org>
Subject: Re: STL problems in GCC 4.1.2
Date: Thu, 21 Feb 2008 22:59:00 -0000 [thread overview]
Message-ID: <8bc817ee0802211459m466df3a4q739815846acb8cf0@mail.gmail.com> (raw)
In-Reply-To: <C3E33851.1C2E%eljay@adobe.com>
On 2/21/08, Eljay Love-Jensen <eljay@adobe.com> wrote:
> Hi Dave,
>
> > The program you gave was entered verbatim, and it compiles with no errors
> > and runs nicely. :)
>
> That indicates to me that the GCC 4.1.2 Standard C++ Library (including the
> STL) is probably working correctly, and something else is causing things to
> go awry.
>
> One possible culprit is that some header file somewhere (not one of the GCC
> 4.1.2 ones) is introducing a #define identifier that is wreaking havoc on
> later #include directives due to identifier collision. You may be able to
> use g++ -E to assess where that is occurring, if it is indeed occurring.
> [This is my first, best guess.]
...
And don't forget Scott Meyers's admonitions to NEVER use a using
declaration inside a header or in a source file before any #include's.
-Tom
next prev parent reply other threads:[~2008-02-21 22:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 22:11 David Arthur
2008-02-12 22:23 ` Tom Browder
2008-02-12 22:46 ` David Arthur
2008-02-12 23:20 ` James Tebneff
2008-02-14 22:23 ` David Arthur
2008-02-21 18:14 ` David Arthur
[not found] ` <C3E329D4.1C1C%eljay@adobe.com>
2008-02-21 19:27 ` David Arthur
2008-02-21 19:43 ` Eljay Love-Jensen
2008-02-21 20:08 ` David Arthur
2008-02-21 20:17 ` Eljay Love-Jensen
2008-02-21 22:59 ` Tom Browder [this message]
2008-02-21 22:59 ` Tom Browder
2008-02-22 9:08 ` Tom Browder
2008-02-25 14:53 ` Philipp Thomas
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=8bc817ee0802211459m466df3a4q739815846acb8cf0@mail.gmail.com \
--to=tom.browder@gmail.com \
--cc=darthur@tantacomm.com \
--cc=eljay@adobe.com \
--cc=gcc-help@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).