From: Stan Sieler <sieler@allegro.com>
To: willy@debian.org (Matthew Wilcox)
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] pdc_add_valid
Date: Fri, 5 Oct 2001 14:58:13 -0700 (PDT) [thread overview]
Message-ID: <200110052158.OAA06081@opus.allegro.com> (raw)
In-Reply-To: <20011005172222.D19206@parcelfarce.linux.theplanet.co.uk> from "Matthew Wilcox" at Oct 05, 2001 05:22:22 PM
Re:
> if (!pdc_add_valid( (void *)(port+4))) {
>
> Which says to me `if this address is not valid' -- the opposite of what it
> does. It could be rewritten as:
Very good point.
Code should be readable first, and efficient second.
Routines that work the opposite of their name are just problems
waiting to happen.
> if (valid_io_addr (port+4)) {
vs:
> + return (pdc_add_valid (addr) == PDC_OK);
The latter has the advantage that the reader knows it's a PDC
routine being called, not some kernel routine that could be done
who knows what.
Thus, I'd go for the latter, or change your "valid_io_addr" to
"pdc_valid_io_addr", to (a) be readable; and (b) convey the PDC info.
Stan (still can't believe HP-UX uses non-compatible "sprintf" in the kernel) Sieler
next prev parent reply other threads:[~2001-10-05 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 16:22 [parisc-linux] pdc_add_valid Matthew Wilcox
2001-10-05 21:58 ` Stan Sieler [this message]
2001-10-05 23:24 ` Matthew Wilcox
2001-10-06 0:26 ` Grant Grundler
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=200110052158.OAA06081@opus.allegro.com \
--to=sieler@allegro.com \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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