public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "poletti.marco at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29234] Call to operator() of temporary object wrongly parsed
Date: Mon, 17 Sep 2012 17:54:00 -0000 [thread overview]
Message-ID: <bug-29234-4-oqbpqefQfL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29234-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29234
poletti.marco at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |poletti.marco at gmail dot
| |com
--- Comment #4 from poletti.marco at gmail dot com 2012-09-17 17:53:36 UTC ---
Still an issue with GCC 4.7.1.
Clang does not have this issue.
next parent reply other threads:[~2012-09-17 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-29234-4@http.gcc.gnu.org/bugzilla/>
2012-09-17 17:54 ` poletti.marco at gmail dot com [this message]
2012-09-17 17:57 ` poletti.marco at gmail dot com
2012-09-17 17:59 ` poletti.marco at gmail dot com
2013-10-30 14:42 ` paolo.carlini at oracle dot com
2013-10-30 17:58 ` paolo.carlini at oracle dot com
2013-11-02 9:34 ` paolo at gcc dot gnu.org
2013-11-02 9:36 ` paolo.carlini at oracle dot com
2014-06-26 19:24 ` paolo.carlini at oracle dot com
2006-09-26 10:40 [Bug c++/29234] New: Cannot put temporary member functor calls inside brackets lloyd dot reed at vistec-semi dot com
2006-10-10 3:51 ` [Bug c++/29234] Call to operator() of temporary object wrongly parsed bangerth at dealii dot org
2007-02-07 5:14 ` lidaobing at gmail dot com
2009-11-13 21:07 ` pinskia at gcc dot gnu 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=bug-29234-4-oqbpqefQfL@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).