This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PING: [PATCH] Implement warning for wrong use of ||/&&

From: "Daniel Franke" <franke dot daniel at gmail dot com>
To: "Manuel López-Ibáñez" <lopezibanez at gmail dot com>
Cc: "Dirk Mueller" <dmueller at suse dot de>, gcc-patches at gcc dot gnu dot org, "Gabriel Dos Reis" <gdr at cs dot tamu dot edu>
Date: Mon, 19 Feb 2007 17:59:05 +0100
Subject: Re: PING: [PATCH] Implement warning for wrong use of ||/&&
References: <200702130009.06245.dmueller@suse.de> <200702191704.37890.dmueller@suse.de> <6c33472e0702190811x7e11703k64271a18d34bd688@mail.gmail.com> <200702191729.01478.dmueller@suse.de> <6c33472e0702190839y4ce4340ewc347b75c8e478cd@mail.gmail.com>

2007/2/19, Manuel López-Ibáñez <lopezibanez@gmail.com>:

I think it still makes sense that -Walways-true warns for things that
are always true or always false. For example, "comparison of unsigned
> 0 is always true" and "comparison of unsigned < 0 is always false"
make sense to be together. However, I don't feel very strong about
this. So, if something else is considered a better name, I can
implement that. Let's hear Gabriel's opinion on this.

As a passer-by, how about "-Wlogical-invariant"?

Daniel

References:
- [PATCH] Implement warning for wrong use of ||/&&
  - From: Dirk Mueller
- Re: PING: [PATCH] Implement warning for wrong use of ||/&&
  - From: Dirk Mueller
- Re: PING: [PATCH] Implement warning for wrong use of ||/&&
  - From: Manuel López-Ibáñez
- Re: PING: [PATCH] Implement warning for wrong use of ||/&&
  - From: Dirk Mueller
- Re: PING: [PATCH] Implement warning for wrong use of ||/&&
  - From: Manuel López-Ibáñez

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]