From: John Love-Jensen <eljay@adobe.com>
To: <gcc-help@gcc.gnu.org>
Subject: Re: GCC compile problem ...
Date: Mon, 30 Sep 2002 04:49:00 -0000 [thread overview]
Message-ID: <B9BDA3BA.4B46%eljay@adobe.com> (raw)
In-Reply-To: <200209280052.38305.sebastian-huber@web.de>
Hi Sebastian,
> I think, that this is not true. If you assign a temporary object to a constant
> reference, the object will survive until the reference is destroyed.
Thanks Sebastian, I stand corrected! A const-reference has lifespan beyond
the full expression.
q.v. Stroustrup's C++PL 3rd ed, section 10.4.10
Sincerely,
--Eljay
Live like you'll die tomorrow. Learn like you'll live forever.
next prev parent reply other threads:[~2002-09-30 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 9:09 gcc
2002-09-27 9:30 ` Sebastian Huber
2002-09-27 9:35 ` John Love-Jensen
2002-09-27 15:52 ` Sebastian Huber
2002-09-30 4:49 ` John Love-Jensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-26 6:51 gcc " Brian J. Dent
2000-01-26 12:10 ` Alexandre Oliva
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Brian J. Dent
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=B9BDA3BA.4B46%eljay@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).