From: Eljay Love-Jensen <eljay@adobe.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Does GCC 3.4 fix this bug?
Date: Thu, 11 Sep 2003 16:07:00 -0000 [thread overview]
Message-ID: <5.2.1.1.0.20030911110503.00bb5d20@iplan-mn.corp.adobe.com> (raw)
Hi everyone,
Does anyone know if this annoying bug in GCC is going to be fixed in 3.4?
--------8<--------
class Foo
{
public:
Foo();
};
Foo::Foo()
{
}
class Bar
{
public:
Bar(const Foo& foo) { }
void print() { }
};
int main()
{
Bar quux(Foo()); // -- Bug in GCC 3.2 & 3.3
//Bar quux((0,Foo())); // -- workaround in GCC 3.2 & 3.3
quux.print();
}
--------8<--------
(Or if GCC 3.2/3.3 are correct, let me know that I'm mistaken about the ISO 14882 standard.)
Thanks,
--Eljay
next reply other threads:[~2003-09-11 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 16:07 Eljay Love-Jensen [this message]
2003-09-11 16:23 ` Nathan Sidwell
2003-09-11 16:44 ` Eljay Love-Jensen
2003-09-11 16:56 ` Nathan Sidwell
2003-09-11 16:37 ` Oliver Kullmann
2003-09-11 16:48 ` Eljay Love-Jensen
2003-09-11 17:06 ` Oliver Kullmann
2003-09-11 17:19 ` Eljay Love-Jensen
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=5.2.1.1.0.20030911110503.00bb5d20@iplan-mn.corp.adobe.com \
--to=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).