From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: gcc@gcc.gnu.org
Subject: Re: [PATCH] fix warning about duplicate 'const'
Date: Wed, 10 Mar 2004 10:30:00 -0000 [thread overview]
Message-ID: <m3fzchvwa4.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0403101010360.22587@digraph.polyomino.org.uk>
"Joseph S. Myers" <jsm@polyomino.org.uk> writes:
| Simpler to restrict the pedwarns for duplicate qualifiers to (pedantic &&
| !flag_isoc99) (in all the various cases warned for) and document this as
| an extension from C99 that is accepted in C89/C90 mode.
I would suggest the existing practice (in nearby language) for this:
(1) reject "direct" duplicate cv-qualifiers, .e.g.
const const int i = 90; // ERROR
(2) accept duplicates that come from typedefs, e.g.
typedef const int T;
const T t = 3889; // OK
and document that as a GNU extension to C90, and compatible with C++.
-- Gaby
next prev parent reply other threads:[~2004-03-10 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200403090043.21043.thomas.schlichter@web.de>
[not found] ` <20040308161410.49127bdf.akpm@osdl.org>
[not found] ` <Pine.LNX.4.58.0403081627450.9575@ppc970.osdl.org>
[not found] ` <200403090217.40867.thomas.schlichter@web.de>
[not found] ` <Pine.LNX.4.58.0403081728250.9575@ppc970.osdl.org>
2004-03-10 5:49 ` Richard Henderson
2004-03-10 6:39 ` Neil Booth
2004-03-10 10:15 ` Joseph S. Myers
2004-03-10 10:30 ` Gabriel Dos Reis [this message]
2004-03-10 22:22 ` Richard Henderson
2004-03-10 23:42 ` Gabriel Dos Reis
2004-03-10 8:21 ` Gabriel Dos Reis
2004-03-10 15:36 ` Linus Torvalds
2004-03-10 18:22 ` Richard Henderson
2004-03-10 18:31 ` Andrew Haley
2004-03-10 18:35 ` Paul Koning
2004-03-10 18:37 ` Richard Henderson
2004-03-16 1:46 ` Mike Stump
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=m3fzchvwa4.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=gcc@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).