public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/48578] Range-based for-loops do not compile when -nostdinc is given Date: Tue, 12 Apr 2011 17:39:00 -0000 [thread overview] Message-ID: <bug-48578-4-VOJIJaVioQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48578-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48578 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-04-12 17:39:15 UTC --- According to the current C++0x draft that loop should call begin(l) and end(l) but there are no declarations of those functions in your testcase, with or without -nostdinc According to the C++0x FDIS your example would work, but that's not implemented in G++ 4.6.0
next prev parent reply other threads:[~2011-04-12 17:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-12 17:14 [Bug c++/48578] New: " jobnoorman at gmail dot com 2011-04-12 17:39 ` redi at gcc dot gnu.org [this message] 2011-04-12 18:29 ` [Bug c++/48578] " jobnoorman at gmail 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-48578-4-VOJIJaVioQ@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: linkBe 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).