public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "johannes.kellner at wandelbots dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109470] unexpected const & behavior
Date: Tue, 11 Apr 2023 09:48:42 +0000	[thread overview]
Message-ID: <bug-109470-4-PQh5ujTnpn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109470-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109470

Johannes Kellner <johannes.kellner at wandelbots dot com> changed:

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

--- Comment #3 from Johannes Kellner <johannes.kellner at wandelbots dot com> ---
'A temporary object bound to a reference parameter in a function call persists
until the completion of the full-expression containing the call.'

So this does not mean, that the temporary object, (int)lenght, should life
until the end of main ??? As main() is the enclosing scope?

  parent reply	other threads:[~2023-04-11  9:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  7:43 [Bug c++/109470] New: " johannes.kellner at wandelbots dot com
2023-04-11  8:25 ` [Bug c++/109470] " xry111 at gcc dot gnu.org
2023-04-11  8:36 ` xry111 at gcc dot gnu.org
2023-04-11  9:48 ` johannes.kellner at wandelbots dot com [this message]
2023-04-11  9:52 ` pinskia at gcc dot gnu.org
2023-04-11  9:56 ` redi at gcc dot gnu.org
2023-04-11 10:23 ` johannes.kellner at wandelbots dot com
2023-04-11 10:36 ` jakub at gcc dot gnu.org
2023-04-11 10:37 ` redi at gcc dot gnu.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=bug-109470-4-PQh5ujTnpn@http.gcc.gnu.org/bugzilla/ \
    --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).