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 10:46:04 +0200 [thread overview]
Message-ID: <20190710084604.GJ21055@port70.net> (raw)
In-Reply-To: <871ryycs9n.fsf@oldenburg2.str.redhat.com>
* Florian Weimer <fweimer@redhat.com> [2019-07-10 08:34:12 +0200]:
> * Szabolcs Nagy:
> > it is clear that 0L is a conforming definition for all
> > conforming c++ compilers.
> >
> > it is less clear if __null is so in all compilers that
> > define __GNUC__.
>
> Why wouldn't something like this be valid for current C++ versions?
if you aim for current c++ only then you need
even more ifdefs (#if __cplusplus > ..).
> static inline constexpr decltype(nullptr) __null{};
> #define NULL __null
>
> I don't see a requirement that NULL must be an expression that can be
> evaluated by the preprocessor.
c++03 requires an integral const expr.,
integral const expr must be usable in #if.
c++11 quietly changed that.
in this case that works out though: undefined
identifiers are 0 in #if, so #if __null works
as expected.
stringification is probably not a valid argument.
next prev parent reply other threads:[~2019-07-10 8:46 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 [this message]
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
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=20190710084604.GJ21055@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).