From: Chip Salzenberg <chip@pobox.com>
To: sneakums@zork.net
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NULL. Again.
Date: Sat, 9 Aug 2003 21:21:29 -0400 [thread overview]
Message-ID: <20030810012129.GA8718@perlsupport.com> (raw)
According to Sean Neakums:
>According to Chip Salzenberg:
>>According to Jamie Lokier:
>>> printf ("%p", NULL);
>>> printf ("%p", 0);
>>
>> 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 had thought that the need for writing NULL [...]
Jeepers, Sean! Why the frell are you subjecting the list to
speculation, when the facts are right there in a URL that you
amazingly enough *quoted* in your speculation-laden message?
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
reply other threads:[~2003-08-10 1:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030810012129.GA8718@perlsupport.com \
--to=chip@pobox.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