From: Timothy Miller <miller@techsource.com>
To: Sean Neakums <sneakums@zork.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NULL. Again. (was Re: [PATCH] 2.4.22pre10: {,un}likely_p())
Date: Mon, 11 Aug 2003 19:06:52 -0400 [thread overview]
Message-ID: <3F38218C.5010407@techsource.com> (raw)
In-Reply-To: 6ufzkad8w1.fsf@zork.zork.net
Sean Neakums wrote:
> Chip Salzenberg <chip@pobox.com> writes:
>
>
>>According to Jamie Lokier:
>>
>>>Not just K&R. These are different because of varargs:
>>> printf ("%p", NULL);
>>> printf ("%p", 0);
>>
>>*SIGH* I thought incorrect folk wisdom about NULL and zero and pointer
>>conversions had long since died out. More fool I. Please, *please*,
>>_no_one_else_ argue about NULL/zero/false etc. until after reading this:
>>
>> ===[[ http://www.eskimo.com/~scs/C-faq/s5.html ]]===
>>
>>I thank you, and linux users everywhere thank you.
>
>
> I had thought that the need for writing NULL where a pointer is
> expected in varags functions was because the machine may have
> different sizes for pointers and int. In the case of the second
> printf call above, if pointers are 64-bit and integers are 32-bit,
> printf will read eight bytes from the stack, and only four will have
> been occupied by the integer 0.
>
Yes, but you're leaving information out. If you read the FAQ, you'll
find that NULL would not be the right thing to use in some cases. For
instance, (char *)0 may be a different value from (void *)0, so it's
best to cast the pointer when passing to printf or something which uses
varargs.
next prev parent reply other threads:[~2003-08-11 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 12:44 [PATCH] 2.4.22pre10: {,un}likely_p() macros for pointers Albert Cahalan
2003-08-09 0:21 ` Jamie Lokier
2003-08-09 8:13 ` Willy Tarreau
2003-08-09 8:51 ` David S. Miller
2003-08-09 9:36 ` Jamie Lokier
2003-08-09 10:10 ` Herbert Xu
2003-08-09 10:42 ` Alan Cox
2003-08-09 16:23 ` Jamie Lokier
2003-08-09 17:30 ` NULL. Again. (was Re: [PATCH] 2.4.22pre10: {,un}likely_p()) Chip Salzenberg
2003-08-09 17:43 ` Sean Neakums
2003-08-11 1:04 ` Jamie Lokier
2003-08-11 23:06 ` Timothy Miller [this message]
2003-08-09 19:44 ` Jamie Lokier
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=3F38218C.5010407@techsource.com \
--to=miller@techsource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sneakums@zork.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).