public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org To: brister@pobox.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@gcc.gnu.org Subject: Re: libstdc++/8231: iostream header position causes bad code generation Date: Mon, 04 Nov 2002 14:32:00 -0000 [thread overview] Message-ID: <20021104223222.12851.qmail@sources.redhat.com> (raw) Synopsis: iostream header position causes bad code generation State-Changed-From-To: analyzed->closed State-Changed-By: ljrittle State-Changed-When: Mon Nov 4 14:32:21 2002 State-Changed-Why: Paolo, if the include of <iostream> is not in position #1, then #include <iosfwd> must appear there, no? It is not legal to move the include of <iostream> out of position #1 in any other case. In any event, with your example, it is not OK to move the include of <iostream> past position #3. Doing so is lying to the compiler. As TC++PL-SE says it, <iosfwd> is sufficient to refer to all things declared in <iostream> but not to apply operations to them. Not a regression but rather a more agressive use of the properties of the standard (in case this worked with libstdc++-v2). http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8231
next reply other threads:[~2002-11-04 22:32 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-04 14:32 ljrittle [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-02 13:43 paolo 2002-11-02 13:16 brister 2002-11-02 12:48 paolo
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=20021104223222.12851.qmail@sources.redhat.com \ --to=ljrittle@gcc.gnu.org \ --cc=brister@pobox.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@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).