On Mon, Sep 04, 2006 at 12:24:41PM +0200, Richard Knutsson wrote:IMO the _Bool is better because that lets the compiler do its magic.
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.
Of course! :) No critisism intended.I took the earlier patch and completed it, switching over to intIs that set in stone? Or is there a chance to (in my opinion) improve the readability, by setting the variables to their real type.
use in place of boolean_t in the few places it used - I'll merge
that at some point, when its had enough testing.
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 theSo, is 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) asHow are you sure "needflush" is, for example, not a counter?
"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...Ok
but, I'll see what the rest of the XFS folks think and take it from
there.
cheers.cu