From: "A. Wilcox" <awilfox@adelielinux.org>
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 15:11:30 -0500 [thread overview]
Message-ID: <ABBDF625-5B9D-4CB5-AEC3-41A7B0DB7E74@adelielinux.org> (raw)
In-Reply-To: <CAA2zVHqcrtM_r-pnDeQf31Lng2n732No5Vc-JPB7w7CM4+jYVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On Jul 10, 2019, at 12:35 PM, James Y Knight <jyknight@google.com> wrote:
>
> It's a question which is impossible to ever answer in the negative -- there always _may be_ any sort of terrible software implemented out there, somewhere. But, I do doubt any such relevant compilers actually exist.
Or, put another way, it has always seemed to me that one of musl's tenets is to "fail fast and break hard" on egregiously invalid code. I'd argue "pretending to be GNU C++ and not having __null" is much more egregious than "code still using NULL in C++". Therefore it's better to break the invalid compiler (which could have any number of other bugs) than break the C++ code.
Sincerely,
--someone who actually enjoys using musl and also actually enjoys using C++, a seemingly rare breed
--
A. Wilcox (Sent from my iPhone - not signed)
Project Lead, Adélie Linux
https://adelielinux.org
[-- Attachment #2: Type: text/html, Size: 1629 bytes --]
next prev parent reply other threads:[~2019-07-10 20:11 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 [this message]
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=ABBDF625-5B9D-4CB5-AEC3-41A7B0DB7E74@adelielinux.org \
--to=awilfox@adelielinux.org \
--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).