public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm at polyomino dot org dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/14313] fail to warn of inconsistent prototype: const char * const vs. const char *
Date: Fri, 27 Feb 2004 14:19:00 -0000	[thread overview]
Message-ID: <20040227141906.20156.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040227010626.14313.wje@acm.org>


------- Additional Comments From jsm at polyomino dot org dot uk  2004-02-27 14:19 -------
Subject: Re:  fail to warn of inconsistent prototype: const char
 * const vs. const char *

On Fri, 27 Feb 2004, rth at gcc dot gnu dot org wrote:

> Not a bug.  6.7.5.3/15: "... corresponding parameters shall have compatible
> types ...", and indeed they are.

The relevant sentence is actually the last one of that paragraph ("... and 
each parameter declared with qualified type is taken as having the 
unqualified version of its declared type").



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14313


  parent reply	other threads:[~2004-02-27 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  1:06 [Bug c/14313] New: gcc i486: " wje at acm dot org
2004-02-27  2:53 ` [Bug c/14313] " pinskia at gcc dot gnu dot org
2004-02-27  8:20 ` rth at gcc dot gnu dot org
2004-02-27 14:09 ` wje at acm dot org
2004-02-27 14:19 ` jsm at polyomino dot org dot uk [this message]
2004-02-27 15:29 ` bangerth at dealii dot 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=20040227141906.20156.qmail@sources.redhat.com \
    --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).