That is error-prone. Not "==FALSE" but what happens if x is (for some reason) not 1 and then "if (x==TRUE)". There has been suggestions of doing:Just would like to ask if you want patches for:Total NACK to any of this boolean ididocy. I very much hope you didn't
get the impression you actually have a chance to get this merged.
* (Most importent, may introduce bugs if left alone)this one of course makes sense, but please do it without introducing
Fixing boolean checking, ex:
if (bool == FALSE)
to
if (!bool)
any boolean type. Getting rid of all the TRUE/FALSE defines and converting
all scsi drivers to classic C integer as boolean semantics would be
very welcome janitorial work.
I don't get it. You object to the 'idiocy' (http://lkml.org/lkml/2006/7/27/281), but find the x==FALSE -> !x a good thing?
Jan EngelhardtRichard Knutsson