[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0607232316420.1638@yvahk01.tjqt.qr>
Date: Sun, 23 Jul 2006 23:17:52 +0200 (MEST)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Jeff Garzik <jeff@...zik.org>
cc: ricknu-0@...dent.ltu.se, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...l.org>,
Alexey Dobriyan <adobriyan@...il.com>,
Vadim Lobanov <vlobanov@...akeasy.net>,
Shorty Porty <getshorty_@...mail.com>,
Peter Williams <pwil3058@...pond.net.au>,
Michael Buesch <mb@...sch.de>,
Pekka Enberg <penberg@...helsinki.fi>,
Stefan Richter <stefanr@...6.in-berlin.de>, larsbj@...lik.net
Subject: Re: [RFC][PATCH] A generic boolean (version 4)
>> > +#define false false
>> > +#define true true
>>
>> Can someone please tell me what advantage 'define true true' is going to
>> bring, besides than being able to '#ifdef true'?
>
> It
>
> (a) makes type information available to the C compiler, where a plain #define
> does not.
Do you mean preprocessor? C already knows about true from the enum.
> (b) handles all '#ifndef true' statements properly
Holy *, is there _really_ code in linux/ that depends on true being
[not] defined?
Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists