public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: porten@kde.org To: gcc-gnats@gcc.gnu.org Subject: c/10480: Bogus warning about non-static const member Date: Thu, 24 Apr 2003 12:26:00 -0000 [thread overview] Message-ID: <20030424121843.13254.qmail@sources.redhat.com> (raw) >Number: 10480 >Category: c >Synopsis: Bogus warning about non-static const member >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Apr 24 12:26:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Harri Porten >Release: gcc 3.2 >Organization: >Environment: i686-pc-linux-gnu >Description: When compiling this piece of code with -W static const struct { const char* const s; } f[] = { { "foo" }, { "bar" } }; the compiler emits the warning: foo.c:2: warning: non-static const member `const char* const <anonymous struct>::s' in class without a constructor Under normal circumstances I think I do understand the warning. But in this particular case instances of the struct a) are initialized explictly b) can't be created by anywhere else because the struct is anonymous So I think the warning is not justified. Harri. >How-To-Repeat: gcc -W foo.c >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-04-24 12:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030424121843.13254.qmail@sources.redhat.com \ --to=porten@kde.org \ --cc=gcc-gnats@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: linkBe 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).