content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: RE: (0 == foo), rather than (foo == 0)
Date: Thu, 11 Mar 2004 09:34:44 +0530
Message-ID: <905989466451C34E87066C5C13DDF034593393@HYDMLVEM01.e2k.ad.ge.com>
Thread-Topic: (0 == foo), rather than (foo == 0)
Thread-Index: AcQHEMR8wDa/yUL1SaeesRuJtYXsCAAC8mZg
From: "Godbole, Amarendra \(GE Consumer & Industrial\)" 
	<Amarendra.Godbole@ge.com>
To: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1032
Lines: 29

> As a result, using the former just tends to increase peoples 
> confusion by making code harder to read, which in turn tends 
> to increase the chance of bugs.

Kindly don't insult the kernel developers' with such statements. ;-)
They are smart enough to understand such constructs, which, I 
deduce from what someone said earlier in this thread. So no 
confusion  would prevail here...[take it in a lighter vein folks, I 
am kidding.]

> So don't do it. The kind of bug that the "0 == x" syntax 
> protects against is LESS LIKELY to happen than the kind of 
> bug it tends to cause.

Agreed and understood. Thanks.

Sincere apologies for my previous ``non-text wrapped'' post. This
won't happen henceforth.

Cheers,
Amarendra

--
Picture Perfect Engineering / These opinions are mine.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/