From: Jeff Garzik <jeff@garzik.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: ricknu-0@student.ltu.se, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Vadim Lobanov <vlobanov@speakeasy.net>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Shorty Porty <getshorty_@hotmail.com>,
Peter Williams <pwil3058@bigpond.net.au>,
Michael Buesch <mb@bu3sch.de>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
larsbj@gullik.net, Paul Jackson <pj@sgi.com>,
Josef Sipek <jsipek@fsl.cs.sunysb.edu>,
Arnd Bergmann <arnd.bergmann@de.ibm.com>,
Nicholas Miell <nmiell@comcast.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Lars Noschinski <cebewee@gmx.de>
Subject: Re: [PATCH 1/2] include/linux: Defining bool, false and true
Date: Tue, 01 Aug 2006 17:48:11 -0400 [thread overview]
Message-ID: <44CFCC1B.8080509@garzik.org> (raw)
In-Reply-To: <44CFCABC.6040406@zytor.com>
H. Peter Anvin wrote:
> Jeff Garzik wrote:
>> H. Peter Anvin wrote:
>>> There is no enum involved.
>> There should be. It makes more information available to the C
>> compiler, and it makes useful symbols available to the debugger.
> _Bool is a native C type; it has all the information the C compiler needs.
"#define true 1" however does not.
Jeff
next prev parent reply other threads:[~2006-08-01 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 12:19 [PATCH 0/2] A generic boolean-type ricknu-0
2006-07-29 12:32 ` [PATCH 1/2] include/linux: Defining bool, false and true ricknu-0
2006-08-01 19:19 ` H. Peter Anvin
2006-08-01 21:12 ` ricknu-0
2006-08-01 21:20 ` H. Peter Anvin
2006-08-01 21:31 ` Jeff Garzik
2006-08-01 21:42 ` H. Peter Anvin
2006-08-01 21:48 ` Jeff Garzik [this message]
2006-08-01 21:52 ` H. Peter Anvin
2006-08-01 21:23 ` Jeff Garzik
2006-08-01 21:41 ` H. Peter Anvin
2006-08-01 21:47 ` Jeff Garzik
2006-07-29 12:36 ` [PATCH 2/2] drivers: Removes colliding boolean definitions ricknu-0
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=44CFCC1B.8080509@garzik.org \
--to=jeff@garzik.org \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd.bergmann@de.ibm.com \
--cc=cebewee@gmx.de \
--cc=getshorty_@hotmail.com \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=larsbj@gullik.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=nmiell@comcast.net \
--cc=penberg@cs.helsinki.fi \
--cc=pj@sgi.com \
--cc=pwil3058@bigpond.net.au \
--cc=ricknu-0@student.ltu.se \
--cc=stefanr@s5r6.in-berlin.de \
--cc=vlobanov@speakeasy.net \
/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.