public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "broken.zhou at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51625] -Wconversion should be on by default, or at least included in -Wall
Date: Sun, 29 Apr 2012 12:17:00 -0000	[thread overview]
Message-ID: <bug-51625-4-8Xt6bWf8V3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51625-4@http.gcc.gnu.org/bugzilla/>

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

Yichao Zhou <broken.zhou at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |broken.zhou at gmail dot
                   |                            |com

--- Comment #4 from Yichao Zhou <broken.zhou at gmail dot com> 2012-04-29 12:16:54 UTC ---
I run into this problem today too.  Why gcc do not warning by default when we
assign a double to a int?  This is even not warned by Wall and Wextra.  If you
google the internet, you will find there are many users asking this question.

> This tied with the fact that there is no data-flow in front-ends (see next question) results in hard to avoid warnings for perfectly working and valid code.

This is not convincing for me.  Since I think you should do these conversion
explicitly to tell others you know what you are doing.

I hope that there is a day that the developer can change their mind on this
question:)


  parent reply	other threads:[~2012-04-29 12:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 17:22 [Bug c++/51625] New: " pnf at podsnap dot com
2011-12-30  6:17 ` [Bug c++/51625] " pinskia at gcc dot gnu.org
2011-12-30  6:19 ` pinskia at gcc dot gnu.org
2011-12-30 17:27 ` pnf at podsnap dot com
2012-04-29 12:17 ` broken.zhou at gmail dot com [this message]
2012-04-29 21:56 ` manu at gcc dot gnu.org
2012-04-30  9:12 ` pnf at podsnap dot com
2012-04-30 10:03 ` redi at gcc dot gnu.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=bug-51625-4-8Xt6bWf8V3@http.gcc.gnu.org/bugzilla/ \
    --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).