This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
c++/713: request for better -Wshadow message
- To: gcc-gnats at gcc dot gnu dot org
- Subject: c++/713: request for better -Wshadow message
- From: tromey at redhat dot com
- Date: 30 Oct 2000 22:21:09 -0000
- Reply-To: tromey at redhat dot com
- Resent-Cc: gcc-prs at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, jason at gcc dot gnu dot org
- Resent-Reply-To: gcc-gnats@gcc.gnu.org, tromey@redhat.com
>Number: 713
>Category: c++
>Synopsis: request for better -Wshadow message
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Oct 30 14:26:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: Tom Tromey
>Release: unknown-1.0
>Organization:
>Environment:
current cvs gcc
RH x86 Linux 6.2
>Description:
When compiling libgcj with -Wshadow I get this warning
repeatedly:
../../../libgcj/libjava/interpret.cc:670: warning: declaration of `index'
shadows global declaration
I don't know where `index' is declared globally.
I'm guessing it is a C string function that somehow
gets declared.
First, I don't really want this warning. I don't care
if I shadow a function name.
Second, and more importantly, it would be nice if
-Wshadow printed the location of the conflicting
declaration. Otherwise I have to use "gcc -E" and dig
backwards from there to find it, which is a pain.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: