From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: [PATCH] Define NULL as __null in C++ mode when using GCC or Clang.
Date: Wed, 10 Jul 2019 23:44:07 +0200 [thread overview]
Message-ID: <20190710214407.GN21055@port70.net> (raw)
In-Reply-To: <20190710211624.GX1506@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2019-07-10 17:16:24 -0400]:
> > i think modern c++ code should use nullptr in the code.
> >
> > definition of NULL should be imo kept as 0L (that's what
> > you would get on older unix systems or on openbsd anyway)
> > apparently some ppl prefer __null.
>
> Do you know if OpenBSD has a reason they do it this way?
hm i misremembered and they changed it anyway
https://github.com/openbsd/src/blob/master/sys/sys/_null.h
openbsd used to define NULL as 0L for both c and c++,
then they changed it to __null if __GNUG__ and 0L and
(void*)0 for c++ and c, now it's even more complicated.
maybe it was some other bsd or solaris that used 0L
i remember looking at it last time we changed NULL.
next prev parent reply other threads:[~2019-07-10 21:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 19:19 James Y Knight
2019-07-09 19:38 ` Rich Felker
2019-07-09 23:04 ` James Y Knight
2019-07-10 2:03 ` Szabolcs Nagy
2019-07-10 6:34 ` Florian Weimer
2019-07-10 8:46 ` Szabolcs Nagy
2019-07-10 16:18 ` James Y Knight
2019-07-10 16:44 ` Rich Felker
2019-07-10 17:35 ` James Y Knight
2019-07-10 20:11 ` A. Wilcox
2019-07-10 20:19 ` Michael Everitt
2019-07-10 20:45 ` Rich Felker
2019-07-10 20:48 ` Rich Felker
2019-07-10 21:11 ` Szabolcs Nagy
2019-07-10 21:16 ` Rich Felker
2019-07-10 21:44 ` Szabolcs Nagy [this message]
2019-07-10 16:01 ` James Y Knight
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=20190710214407.GN21055@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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/musl/
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).