From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29077 invoked by alias); 29 Sep 2011 07:18:17 -0000 Received: (qmail 29012 invoked by uid 22791); 29 Sep 2011 07:18:15 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Sep 2011 07:18:01 +0000 From: "ethouris at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50563] New: Weird syntax acceptance rules for non-static data members initialized in place (C++0x) Date: Thu, 29 Sep 2011 08:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ethouris at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-09/txt/msg02208.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D50563 Bug #: 50563 Summary: Weird syntax acceptance rules for non-static data members initialized in place (C++0x) Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: ethouris@gmail.com In the latest version it's possible to initialize data in place. According to the standard, non-static data members can be initialized with: int a =3D 0; or int a {0}; and not with the constructor syntax: int a (0); However there are probably no strict rules how the "list of variables" can = be initialized. I state that it should be normally allowed. Actually gcc accep= ts the following syntax: int a {10}, b {20}; as well as: int a, b =3D 20; but this one: int a =3D 10, b =3D 20; ends up with the following error message: error: expected =E2=80=98;=E2=80=99 before =E2=80=98,=E2=80=99 token I'm not completely sure, but it should be just strict rule: either the list= of variables syntax is not allowed when the variables are also initialized (so= int a,b=3D20; should fail too), or the list of variables syntax should be suppo= rted as usual.