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/17654] Pointless warning on incompatible pointer types
Date: Mon, 27 Sep 2004 15:32:00 -0000	[thread overview]
Message-ID: <20040927153245.16516.qmail@sourceware.org> (raw)
In-Reply-To: <20040924151647.17654.jbeulich@novell.com>


------- Additional Comments From jsm at polyomino dot org dot uk  2004-09-27 15:32 -------
Subject: Re:  Pointless warning on incompatible pointer types

On Mon, 27 Sep 2004, jbeulich at novell dot com wrote:

> Thus I continue to believe that this is an omission on the part of the standard,
> and would hence want to see gcc provide at least an optional way to circumvent
> this problem.

That way at present is to use the C++ compiler, if you want the C++ 
const-correctness rules.  Such a change was proposed for C99 in 
<http://www.open-std.org/JTC1/SC22/WG14/www/docs/n754.htm>.  I do not know 
why it was not adopted although the impression I get is that it was 
proposed too late in the process and there wasn't enough time at the 
relevant meeting.  I would suggest it might be worth proposing such a 
change again when features for C1x are under consideration in some years' 
time; C++ provides the prior art.



-- 


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


  parent reply	other threads:[~2004-09-27 15:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24 15:16 [Bug c/17654] New: " jbeulich at novell dot com
2004-09-24 15:51 ` [Bug c/17654] " pinskia at gcc dot gnu dot org
2004-09-27  7:50 ` jbeulich at novell dot com
2004-09-27 13:39 ` pinskia at gcc dot gnu dot org
2004-09-27 15:14 ` jbeulich at novell dot com
2004-09-27 15:24 ` bangerth at dealii dot org
2004-09-27 15:32 ` jbeulich at novell dot com
2004-09-27 15:32 ` jsm at polyomino dot org dot uk [this message]
2004-09-27 15:50 ` pinskia at gcc dot gnu dot org
2004-09-27 15:50 ` schwab at suse dot de

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=20040927153245.16516.qmail@sourceware.org \
    --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).