public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Jeffrey Turner" <jturner@mail.alum.rpi.edu>
To: nathan@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5089: -Wold-style-cast warns about cast to void
Date: Wed, 02 Jan 2002 10:56:00 -0000	[thread overview]
Message-ID: <20020102185601.16456.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/5089; it has been noted by GNATS.

From: "Jeffrey Turner" <jturner@mail.alum.rpi.edu>
To: <gcc-bugs@gcc.gnu.org>,
    <gcc-prs@gcc.gnu.org>,
    <llib@computer.org>,
    <nathan@gcc.gnu.org>,
    mputer.org@LOCALHOST,
    <nathan@gcc.gnu.org>
Cc:  
Subject: Re: c++/5089: -Wold-style-cast warns about cast to void
Date: Wed,  2 Jan 2002 14:02:59 -0500

 >Synopsis: -Wold-style-cast warns about cast to void
 >
 >State-Changed-From-To: analyzed->closed
 >State-Changed-By: nathan
 >State-Changed-When: Wed Jan  2 05:59:02 2002
 >State-Changed-Why:
 >    2002-01-02  Nathan Sidwell  <nathan@codesourcery.com>
 >    
 >    	PR c++/5089
 >    	* doc/invoke.texi (-Wold-style-cast): Only warn about non-void casts.
 >    
 >    2002-01-02  Nathan Sidwell  <nathan@codesourcery.com>
 >    
 >    	PR c++/5089
 >    	* decl2.c (reparse_absdcl_as_casts): Don't warn about casts to void.
 
 I still think this is a mistake.  If I want to be warned
 about old-style casts then the compiler should _always_
 oblige.  It should be up to the programmer whether or not
 to ignore compiler warnings.  That was the premise of C.
 I still think it's valid to let the programmer decide
 rather than the stupid compiler.  How else will we catch
 all the archaic code that hopefully should be eliminated?
 
 --Jeff Turner
 
 Who put the Sam in the "'Sama Laden Ding-Dong"?
                  


             reply	other threads:[~2002-01-02 18:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02 10:56 Jeffrey Turner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-02  5:59 nathan
2001-12-30  8:26 Nathan Sidwell
2001-12-29  7:06 Nathan Sidwell
2001-12-29  5:56 Jeffrey Turner
2001-12-27 13:09 nathan
2001-12-18 14:23 nathan
2001-12-11 22:46 llib

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=20020102185601.16456.qmail@sources.redhat.com \
    --to=jturner@mail.alum.rpi.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nathan@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).