From: jw schultz <jw@pegasys.ws>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][TRIVIAL] Bugzilla bug # 322 - double logical operator drivers/char/sx.c
Date: Thu, 7 Aug 2003 16:02:52 -0700 [thread overview]
Message-ID: <20030807230252.GJ1380@pegasys.ws> (raw)
In-Reply-To: <200308070420.45464.jeffpc@optonline.net>
On Thu, Aug 07, 2003 at 04:20:37AM -0400, Jeff Sipek wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wednesday 06 August 2003 20:35, Timothy Miller wrote:
> > Josef 'Jeff' Sipek wrote:
> > > Just a simple fix to make the statements more readable. (instead of
> > > "i < TIMEOUT > 0" the statement is divided into two, joined by &&.)
> >
> > Can you really DO (x < y > z) and have it work as an anded pair of
> > comparisons? Maybe this is an addition to C that I am not aware of.
> >
> > I would expect (x < y > z) to be equivalent to ((x < y) > z).
>
> Odd, this has been in the kernel ever since Linus started using BK. I didn't
> check pre-BK. I wonder what the author intended to say. (I believe in the
> ((a<b) && (b>c)) theory.)
I've got an old system with 2.2.10 and took a look. It
appears as though the form of the loop in may of 1999 was
for(delay = SX_CCR_TIMEOUT; delay; delay--)
so my guess is that the changes were made around the
constant to minimise typing and progressed something like so:
for(delay = SX_CCR_TIMEOUT; delay; delay--)
for(delay = SX_CCR_TIMEOUT; delay > 0; delay--)
for(delay = 0; delay < SX_CCR_TIMEOUT > 0; delay++)
with name changes somewhere in the mix. So there was never
any intent to have a double test. Besides comparing a
constant with another constant wouldn't make much sense.
--
________________________________________________________________
J.W. Schultz Pegasystems Technologies
email address: jw@pegasys.ws
Remember Cernan and Schmitt
next prev parent reply other threads:[~2003-08-07 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 22:30 Josef 'Jeff' Sipek
2003-08-07 0:32 ` Krzysztof Halasa
2003-08-07 0:35 ` Timothy Miller
2003-08-07 1:26 ` Jeff Sipek
2003-08-07 3:12 ` Valdis.Kletnieks
2003-08-07 4:00 ` Rahul Karnik
2003-08-07 4:12 ` Rahul Karnik
2003-08-07 1:29 ` Josef 'Jeff' Sipek
2003-08-07 8:20 ` Jeff Sipek
2003-08-07 23:02 ` jw schultz [this message]
2003-12-21 6:55 Josef 'Jeff' Sipek
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=20030807230252.GJ1380@pegasys.ws \
--to=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®