public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/18272] weird behaviour on temporary return values
Date: Tue, 02 Nov 2004 14:14:00 -0000	[thread overview]
Message-ID: <20041102141455.11094.qmail@sourceware.org> (raw)
In-Reply-To: <20041102123746.18272.philippe.haution@mines-paris.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-11-02 14:14 -------
I think this is correct and here is why:
    auto_ptr<vector<int> > res1 = ert(); // OK  <-- we call the copy construtor so we increment the 
refence
    vector<int>& res2 = *res1;           // OK  <-- this is reference already


    vector<int> *res3 = ert().get();     // NOK  <-- we don't increment the reference so we will free it
 right after this statement has been executated

    vector<int>& res4 = *(ert());        // NOK if res5 not created afterwards 
<---- same as above


    vector<int>& res5 = *(ert().release());// OK
  <--- should have caused an exeception as you are already freed it

temporary return values only last untill the statement is finished.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18272


  reply	other threads:[~2004-11-02 14:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 12:38 [Bug c++/18272] New: " philippe dot haution at mines-paris dot org
2004-11-02 14:14 ` pinskia at gcc dot gnu dot org [this message]
2004-11-02 14:54 ` [Bug c++/18272] " philippe dot haution at mines-paris dot org
2004-11-02 14:57 ` pinskia at gcc dot gnu dot org
2004-11-02 15:58 ` philippe dot haution at mines-paris dot org

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=20041102141455.11094.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).