From: Nathan Scott <nathans@sgi.com>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: akpm@osdl.org, xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18-rc4-mm3 2/2] fs/xfs: Converting into generic boolean
Date: Tue, 5 Sep 2006 13:05:57 +1000 [thread overview]
Message-ID: <20060905130557.A3334712@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <44FBFEE9.4010201@student.ltu.se>; from ricknu-0@student.ltu.se on Mon, Sep 04, 2006 at 12:24:41PM +0200
On Mon, Sep 04, 2006 at 12:24:41PM +0200, Richard Knutsson wrote:
> Nathan Scott wrote:
> >Hmm, so your bool is better than the next guys bool[ean[_t]]? :)
> Well yes, because it is not "mine". ;)
> It is, after all, just a typedef of the C99 _Bool-type.
Hmm, one is really no better than the other IMO.
> >I took the earlier patch and completed it, switching over to int
> >use in place of boolean_t in the few places it used - I'll merge
> >that at some point, when its had enough testing.
> >
> Is that set in stone? Or is there a chance to (in my opinion) improve
> the readability, by setting the variables to their real type.
Nothings completely "set in stone" ... anyone can (and does) offer
their own opinion. The opinion of people who a/ read and write XFS
code alot and b/ test their changes, is alot more interesting than
the opinion of those who don't, however.
In reality, from an XFS point of view, there are so few uses of the
local boolean_t and so little value from it, that it really is just
not worth getting involved in the pending bool code churn IMO (I see
72 definitions of TRUE and FALSE in a recent mainline tree, so you
have your work cut out for you...).
"int needflush;" is just as readable (some would argue moreso) as
"bool needflush;" and thats pretty much the level of use in XFS -
and we're using the "int" form in so many other places anyway...
but, I'll see what the rest of the XFS folks think and take it from
there.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-09-05 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 13:21 Richard Knutsson
2006-09-04 5:02 ` Nathan Scott
2006-09-04 10:24 ` Richard Knutsson
2006-09-05 3:05 ` Nathan Scott [this message]
2006-09-05 12:47 ` Richard Knutsson
2006-09-05 23:14 ` [xfs-masters] " Nathan Scott
2006-09-06 0:23 ` Richard Knutsson
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=20060905130557.A3334712@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricknu-0@student.ltu.se \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/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®