[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0703120229030.18623@yvahk01.tjqt.qr>
Date: Mon, 12 Mar 2007 02:32:00 +0100 (MET)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Kyle Moffett <mrmacman_g4@....com>
cc: Daniel Hazelton <dhazelton@...er.net>,
Cong WANG <xiyou.wangcong@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: Style Question
On Mar 11 2007 21:27, Kyle Moffett wrote:
> On Mar 11, 2007, at 19:16:59, Jan Engelhardt wrote:
>> On Mar 11 2007 18:01, Kyle Moffett wrote:
>> > On the other hand when __cplusplus is defined they define it to the
>> > "__null" builtin, which GCC uses to give type conversion errors for
>> > "int foo = NULL" but not "char *foo = NULL".
>> I think that the primary reason they use __null is so that you can
>> actually do[...]
>
> Isn't that what I said? :-D
Ya. Though I was picking at
|"__null" builtin, which GCC uses to give type conversion errors for
|"int foo = NULL"
since C's (void *)0 would also barf when being assigned to int.
So it's not a genuine __null feature ;-)
Jan
--
-
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