public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "denis.campredon at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114265] New: Unhelpful message when var name is also a struct name
Date: Thu, 07 Mar 2024 09:12:04 +0000	[thread overview]
Message-ID: <bug-114265-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114265

            Bug ID: 114265
           Summary: Unhelpful message when var name is also a struct name
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: denis.campredon at gmail dot com
  Target Milestone: ---

While working with legacy code, I encountered the following problem.

The code:
------------
struct Struct;

int fn(Struct *);

Struct *Struct;

int fn(Struct *)
{ 
    return 0;
}
-------------
produces the following error message:
-------------
aaaaaa.c:7:8: error: 'int fn' redeclared as different kind of entity
    7 | int fn(Struct *)
      |        ^~~~~~
aaaaaa.c:3:5: note: previous declaration 'int fn(Struct*)'
    3 | int fn(Struct *);
      |     ^~
aaaaaa.c:7:16: error: expected primary-expression before ')' token
    7 | int fn(Struct *)
--------------

This message does not really explain what the real problem is.
A message saying that `Struct` has been redefined as a variable would help
more.

             reply	other threads:[~2024-03-07  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  9:12 denis.campredon at gmail dot com [this message]
2024-03-07 11:57 ` [Bug c++/114265] " redi 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-114265-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).