public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tclamb at ufl dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54430] [C++11] For-Loop: Scope of iterating variable begins too early
Date: Fri, 28 Mar 2014 14:15:00 -0000 [thread overview]
Message-ID: <bug-54430-4-h1qzrkVJbw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54430-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54430
Thomas Lamb <tclamb at ufl dot edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tclamb at ufl dot edu
--- Comment #1 from Thomas Lamb <tclamb at ufl dot edu> ---
Just hit this bug in GCC 4.9. Again, the lhs side has scope before the rhs has
been evaluated, which is against the standardese in section 6.5.4 of both N3936
and N3291.
next prev parent reply other threads:[~2014-03-28 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 23:08 [Bug c++/54430] New: [C++11] Range Based For Loop lhs scoping issue mrks at koios dot de
2014-03-28 14:15 ` tclamb at ufl dot edu [this message]
2014-03-28 14:16 ` [Bug c++/54430] [C++11] For-Loop: Scope of iterating variable begins too early ppluzhnikov at google dot com
2014-03-28 14:17 ` ppluzhnikov at google dot com
2014-03-28 17:29 ` redi at gcc dot gnu.org
2015-08-09 7:49 ` akim.demaille at gmail dot com
2015-08-09 7:51 ` akim.demaille at gmail dot com
2015-08-17 0:52 ` miyuki at gcc dot gnu.org
2015-09-15 10:16 ` redi at gcc dot gnu.org
2015-10-01 19:22 ` ville at gcc dot gnu.org
2015-10-01 19:24 ` ville.voutilainen at gmail dot com
2015-10-05 8:53 ` paolo.carlini at oracle dot com
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-54430-4-h1qzrkVJbw@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).