public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "james.kanze at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53434] New: Compiler decides declaration/expression ambiguity too soon.
Date: Mon, 21 May 2012 12:43:00 -0000	[thread overview]
Message-ID: <bug-53434-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53434
           Summary: Compiler decides declaration/expression ambiguity too
                    soon.
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: james.kanze@gmail.com


Created attachment 27459
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27459
Source code for very simple program showing the bug.

This may be the same as 37213, but the context is somewhat different.  When I
compile (simply g++ -c <filename>), I get the following error message:

bugInGcc.cc: In function 'void f()':
bugInGcc.cc:20:39: error: size of array has non-integral type 'const char [2]'
bugInGcc.cc:20:39: error: 'parameter' declared as function returning an array

Apparently, g++ is deciding in favor of declaration after seeing C()["a"],
despite the fact that a declaration cannot be followed by a . operator.


             reply	other threads:[~2012-05-21 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 12:43 james.kanze at gmail dot com [this message]
2012-05-26 23:48 ` [Bug c++/53434] " pinskia at gcc dot gnu.org
2021-07-24  2:36 ` pinskia 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-53434-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).