public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ace.of.zerosync at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29834] g++ thinks it is a declaration when it cannot be
Date: Tue, 02 Jul 2013 12:10:00 -0000	[thread overview]
Message-ID: <bug-29834-4-q6166V8YqW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29834-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from M.S. Babaei <ace.of.zerosync at gmail dot com> ---
(In reply to Jonathan Wakely from comment #7)
> You can use list-initialization to workaround it:
> 
>   Doh{x}, ++x;

Thanks for the reply. Yeah, it did the trick for GCC 4.4+. And, I've never
thought of that.

But this is a bug, and I see no reason why it hasn't been fixed anyway.
However, your solution works fine with only C++11 enabled projects. Although,
this is not a problem for me, because it has been virtually three years that my
default mode for any new project is C++11. But, it might still be a problem for
others.

Thanks again, you saved me a lot of headaches.


  parent reply	other threads:[~2013-07-02 12:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-29834-4@http.gcc.gnu.org/bugzilla/>
2012-10-11 21:54 ` pinskia at gcc dot gnu.org
2013-07-02 10:25 ` ace.of.zerosync at gmail dot com
2013-07-02 10:49 ` redi at gcc dot gnu.org
2013-07-02 12:10 ` ace.of.zerosync at gmail dot com [this message]
2013-07-02 15:04 ` james.kanze at gmail dot com
2013-07-02 17:16 ` manu at gcc dot gnu.org
2013-07-02 21:38 ` ace.of.zerosync at gmail dot com
2013-07-02 21:48 ` ace.of.zerosync at gmail dot com
2013-07-13  1:53 ` ace.of.zerosync at gmail dot com
2024-02-07 17:36 ` pinskia at gcc dot gnu.org
2024-02-07 17:57 ` mpolacek at gcc dot gnu.org
2006-11-14 16:36 [Bug c++/29834] New: " james dot kanze at gmail dot com
2006-11-14 21:33 ` [Bug c++/29834] " rguenth at gcc dot gnu dot org
2006-11-15  1:59 ` bangerth at dealii dot org
2006-11-15 10:05 ` james dot kanze at gmail dot com
2006-11-15 10:10 ` james dot kanze 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-29834-4-q6166V8YqW@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).