From: Richard Knutsson <ricknu-0@student.ltu.se>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] what's the deal with using real "boolean" variables?
Date: Wed, 10 Jan 2007 11:37:17 +0000 [thread overview]
Message-ID: <45A4CFED.8060200@student.ltu.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0701100337460.11933@localhost.localdomain>
walter harms wrote:
> hi,
> i took a dive into the 'c reference manual' and found that the header stdbool.h
> defines (#define) bool/true/false. It is permited to undefine and redefine these
> defines. It defines also the macro "__bool_true_false_are_defined".
> The best ways seems to emulate this way and provide a kernelbased stdbool.h if
> "__bool_true_false_are_defined" does not exist.
>
Why "__bool_true_false_are_defined" when we _know_ it is defined? Since
2.6.15 (I believe), only gcc >= 3.2 is supported, and from version 3,
gcc supports _Boole.
I first thought to implement it as stdbool.h, but the consensus seems to
be: types in linux/types.h and false/true found a home in linux/stddef.h.
/Richard Knutsson
PS
Please don't top-post. :)
DS
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-01-10 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 8:44 [KJ] what's the deal with using real "boolean" variables? Robert P. J. Day
2007-01-10 9:23 ` Robert P. J. Day
2007-01-10 9:24 ` Richard Knutsson
2007-01-10 9:48 ` Richard Knutsson
2007-01-10 9:53 ` Alexey Dobriyan
2007-01-10 10:17 ` Richard Knutsson
2007-01-10 10:31 ` Bernd Petrovitsch
2007-01-10 10:57 ` walter harms
2007-01-10 11:10 ` Richard Knutsson
2007-01-10 11:37 ` Richard Knutsson [this message]
2007-01-10 13:34 ` Robert P. J. Day
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=45A4CFED.8060200@student.ltu.se \
--to=ricknu-0@student.ltu.se \
--cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.