public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i.nixman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/50736] New: ISO_IEC_14882-2011-5.1.2/10 - bug
Date: Sat, 15 Oct 2011 09:28:00 -0000	[thread overview]
Message-ID: <bug-50736-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50736
           Summary: ISO_IEC_14882-2011-5.1.2/10 - bug
    Classification: Unclassified
           Product: gcc
           Version: 4.6.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: i.nixman@gmail.com


Quote from ISO_IEC_14882-2011, 5.1.2/10:
> The identifiers in a capture-list are looked up using 
> the usual rules for unqualified name lookup (3.4.1); each
> such lookup shall find a variable with automatic 
> storage duration declared in the reaching scope of the local
> lambda expression. An entity (i.e. a variable or this) is 
> said to be explicitly captured if it appears in the
> lambda-expression’s capture-list.

But this code successfuly compiled on gcc-4.6.1:
#include <iostream>
int main() {
  using std::cout;
  auto f = [&cout]() { cout << 1; }; // <<
  f();
}

http://liveworkspace.org/code/ae698b7daf7b5b531beafd9faaa6a409


Intel C++ 12.1 says: error : a variable with static storage
duration cannot be captured in a lambda


niXman.


             reply	other threads:[~2011-10-15  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-15  9:28 i.nixman at gmail dot com [this message]
2011-10-15 20:51 ` [Bug c++/50736] [C++0x] " paolo.carlini at oracle dot com
2011-10-17 19:00 ` jason at gcc dot gnu.org
2011-10-17 19:01 ` jason 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-50736-4@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).