From: Nathan Scott <nathans@sgi.com>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: akpm@osdl.org, xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [xfs-masters] Re: [PATCH 2.6.18-rc4-mm3 2/2] fs/xfs: Converting into generic boolean
Date: Wed, 6 Sep 2006 09:14:08 +1000 [thread overview]
Message-ID: <20060906091407.M3365803@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <44FD71C6.20006@student.ltu.se>; from ricknu-0@student.ltu.se on Tue, Sep 05, 2006 at 02:47:02PM +0200
On Tue, Sep 05, 2006 at 02:47:02PM +0200, Richard Knutsson wrote:
> Just the notion: "your" guys was the ones to make those to boolean(_t),
Sort of, we actually inherited that type from IRIX where it is
defined in <sys/types.h>.
> and now you seem to want to patch them away because I tried to make them
> more general.
Nah, I just don't see the value either way, and see it as another
code churn exercise.
> So, is the:
> B_FALSE -> false
> B_TRUE -> true
> ok by you?
Personally, no. Thats code churn with no value IMO.
> >"int needflush;" is just as readable (some would argue moreso) as
> >"bool needflush;" and thats pretty much the level of use in XFS -
> >
> How are you sure "needflush" is, for example, not a counter?
Well, that would be named "flushcount" or some such thing. And you
would be able to tell that it was a counter by the way its used in
the surrounding code.
This discussion really isn't going anywhere useful; I think you need
to accept that not everyone sees value in a boolean type. :)
cheers.
--
Nathan
next parent reply other threads:[~2006-09-05 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44F833C9.1000208@student.ltu.se>
[not found] ` <20060904150241.I3335706@wobbly.melbourne.sgi.com>
[not found] ` <44FBFEE9.4010201@student.ltu.se>
[not found] ` <20060905130557.A3334712@wobbly.melbourne.sgi.com>
[not found] ` <44FD71C6.20006@student.ltu.se>
2006-09-05 23:14 ` Nathan Scott [this message]
2006-09-06 0:23 ` [xfs-masters] Re: [PATCH 2.6.18-rc4-mm3 2/2] fs/xfs: Converting into generic boolean 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=20060906091407.M3365803@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@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