public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com> To: nathan@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/5089: -Wold-style-cast warns about cast to void Date: Sun, 30 Dec 2001 08:26:00 -0000 [thread overview] Message-ID: <20011230162602.7738.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/5089; it has been noted by GNATS. From: Nathan Sidwell <nathan@codesourcery.com> To: jturner <jturner@mail.alum.rpi.edu> Cc: nathan <nathan@gcc.gnu.org>, gcc-gnats <gcc-gnats@gcc.gnu.org>, gcc <gcc@gcc.gnu.org>, law <law@gcc.gnu.org>, dosreis <dosreis@cmla.ens-cachien.fr> Subject: Re: c++/5089: -Wold-style-cast warns about cast to void Date: Sun, 30 Dec 2001 16:17:33 +0000 Jeffrey Turner wrote: > >This question came up recently on a gcc mailing list. > >Is there a C++ way to cast something to a void? You're missing the point. No one claimed that static_cast<void> (foo) was wrong. The problem is a) the assert macro b) static_cast<void> (foo) is a mouthful which obscures what you're trying to do. thinks: why am I ignoring the result of a static_cast?, oh I see the target type is void. Much more up front is to have the 'void' at the start of the expression. void is a singularity in the type system, and I beleive -Wold-style-cast should treat it as such. nathan -- Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC 'But that's a lie.' - 'Yes it is. What's your point?' nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next reply other threads:[~2001-12-30 16:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-30 8:26 Nathan Sidwell [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-02 10:56 Jeffrey Turner 2002-01-02 5:59 nathan 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=20011230162602.7738.qmail@sources.redhat.com \ --to=nathan@codesourcery.com \ --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: 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).