From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: 0 vs. NULL (RE: Worrisome warnings after recent patches)
Date: Thu, 4 Mar 1999 11:42:10 +0100 (MET) [thread overview]
Message-ID: <199903041042.LAA02458@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Bruce Stephens's message of 04 Mar 1999 10:35:16 +0000
Bruce Stephens wrote:
> Bernd Eggink <eggink@uni-hamburg.de> writes:
>
> > Andrej Borsenkow wrote:
>
> > > What is the point of using NULL to initialize null pointer. The only
> > > portable and official way is to use `0'(zero), that is garanteed to be
> > > converted to whatever representation null pointer has on a given system.
> >
> > No, this applies to C++ only, not to C. In C you should use the NULL
> > macro or (void*)0.
>
> There's an issue with arguments to functions which don't have
> prototypes, but apart from that, the literal 0 as a pointer should be
> fine in C.
Since the original message was a reaction to my patch: I know that `0'
should be fine in C (at least with modern compilers) and personally I
prefer it. But using `NULL' is the convention used throughout the zsh
code, so...
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-03-04 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-04 10:42 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-04 7:50 Worrisome warnings after recent patches Sven Wischnowsky
1999-03-04 8:31 ` 0 vs. NULL (RE: Worrisome warnings after recent patches) Andrej Borsenkow
1999-03-04 8:42 ` Bernd Eggink
1999-03-04 10:35 ` Bruce Stephens
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=199903041042.LAA02458@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).