From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2988 invoked by alias); 19 Feb 2007 19:48:20 -0000 Received: (qmail 2938 invoked by alias); 19 Feb 2007 19:48:09 -0000 Date: Mon, 19 Feb 2007 19:48:00 -0000 Message-ID: <20070219194809.2937.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/30860] Should warn about boolean constant false used in pointer context In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "gdr at cs dot tamu dot edu" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-02/txt/msg02221.txt.bz2 ------- Comment #4 from gdr at cs dot tamu dot edu 2007-02-19 19:48 ------- Subject: Re: Should warn about boolean constant false used in pointer context "pinskia at gcc dot gnu dot org" writes: | I don't see why we should warn about a very valid and well defined and will | always work on every compiler. You want to warn about a specific coding style | which I think is wrong in this case (and in the -Weffc++ case). The code may be well-formed C++, but it certainly is a candidate for either a conceptual error (or typo) or part of obfuscated code contest. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30860