From: NightStrike <nightstrike@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Better diagnostic for shadowed function?
Date: Wed, 12 Jan 2022 13:36:27 -0500 [thread overview]
Message-ID: <CAF1jjLsATz+t6idB_RRfGTfjLPpg-oD26zgv48GL+vq0ihnrFQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRBPmpB2MS+enUh7rF4aS9QC_hbkONmRT4YaCMV6pDbxw@mail.gmail.com>
On Wed, Jan 12, 2022 at 5:06 AM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> On Wed, 12 Jan 2022 at 06:34, NightStrike via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
> >
> > I recently hit this problem:
> >
> > #include <strings.h>
> > void f() {
> > index[0] = 0;
> > }
> >
> > #gcc is 11.2.0
> > gcc -c a.c
> > a.c:4:7: error: subscripted value is neither array nor pointer nor vector
> > 4 | index[1] = 0;
> > | ^
> >
> > -Wshadow (or all or extra) did not highlight that "index" was actually
> > a function from strings.h. For the future, is there anything I could
> > have done to make gcc tell me what the real error was?
>
> g++ is *slightly* more help:
> s.c:3:10: error: invalid types ‘<unresolved overloaded function
> type>[int]’ for array subscript
>
> This at least gives you a hint it's a function, so probably declared
> somewhere in a header. The C front end could do the same, saying
> "subscripted value is a function", but it just has a generic
> diagnostic for all un-subscriptable types. Asking for that to be
> improved seems like a good use of a bugzilla PR.
>
> Maybe would make sense for us to also add a note telling you where
> 'index' was declared, as long as it doesn't get suppressed without
> -Wsystem-headers !
Added as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103996
Thanks!
prev parent reply other threads:[~2022-01-12 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 6:33 NightStrike
2022-01-12 8:32 ` Xi Ruoyao
2022-01-12 10:06 ` Jonathan Wakely
2022-01-12 18:36 ` NightStrike [this message]
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=CAF1jjLsATz+t6idB_RRfGTfjLPpg-oD26zgv48GL+vq0ihnrFQ@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).