From: Eljay Love-Jensen <eljay@adobe.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Does GCC 3.4 fix this bug?
Date: Thu, 11 Sep 2003 16:44:00 -0000 [thread overview]
Message-ID: <5.2.1.1.0.20030911113059.00bb4a18@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <3F60A10A.2010802@codesourcery.com>
Hi Nathan,
>quux is a function taking a (pointer to function taking no args, returning a Foo) argument and returning a Bar
I realize that's what the compiler is interpreting it as. But I believe that the compiler's interpretation of the code is incorrect.
MSVC (that bastion of standards compliance -- NOT!), and CodeWarrior interpret the code as the variable quux using the const Foo& constructor of Bar.
I don't have the EDG compiler at my disposal, and my Comeau C++ compiler is from 1990 (*grin*).
--Eljay
next prev parent reply other threads:[~2003-09-11 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 16:07 Eljay Love-Jensen
2003-09-11 16:23 ` Nathan Sidwell
2003-09-11 16:44 ` Eljay Love-Jensen [this message]
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.20030911113059.00bb4a18@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nathan@codesourcery.com \
/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).