From: "Rupert Wood" <me@rupey.net>
To: "'Joe Buck'" <Joe.Buck@synopsys.COM>,
"'Phil Prentice'" <philp.cheer@btinternet.com>
Cc: <gcc-help@gnu.org>, <gcc@gnu.org>
Subject: RE: Copy Constructor Problem with 3.2.2??
Date: Fri, 18 Jun 2004 17:29:00 -0000 [thread overview]
Message-ID: <E1BbNAj-000Oi3-0Y@anchor-post-34.mail.demon.net> (raw)
In-Reply-To: <20040618092045.A1619@synopsys.com>
Joe Buck wrote:
> > I have knocked up a simple program that demonstrates this problem.
> > I have compiled this same program using Visual C++ (windows) and
> > it compiles & runs as I would have expected.
> Then you should send a bug report to Microsoft. If the compiler
> accepts an attempt to bind a non-const reference to a temporary,
> this is a serious error in the compiler.
It's a documented extension. The example does raise a level 4 warning
http://msdn.microsoft.com/library/en-us/vccore/html/C4239.asp
and won't compile if you turn off extensions with flag '/Za'.
Rup.
next prev parent reply other threads:[~2004-06-18 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BbHDo-0007oa-4a@monty-python.gnu.org>
2004-06-18 11:17 ` Giovanni Bajo
2004-06-18 16:20 ` Joe Buck
2004-06-18 17:29 ` Rupert Wood [this message]
2004-06-18 11:15 Jyotirmoy Das
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 11:01 Phil Prentice
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=E1BbNAj-000Oi3-0Y@anchor-post-34.mail.demon.net \
--to=me@rupey.net \
--cc=Joe.Buck@synopsys.COM \
--cc=gcc-help@gnu.org \
--cc=gcc@gnu.org \
--cc=philp.cheer@btinternet.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).