From: Richard Yao <ryao@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] C++ standard in ebuilds
Date: Tue, 18 Sep 2018 08:46:46 -0400 [thread overview]
Message-ID: <812A3F5E-AA6A-4FFA-BF70-EE8B6565A6DF@gentoo.org> (raw)
In-Reply-To: <3229421.CvTK6SVxHl@tp>
> On Sep 17, 2018, at 12:40 PM, Vadim A. Misbakh-Soloviov <gentoo@mva.name> wrote:
>
> I'd prefer to wait another replies on the list for the main theme of this e-
> mail, but this problem also affects C (so, as **c**flags and C standards), so
> solution shoudn't be c++ specific, imho.
You would think that, but the C standard version does not effect ABI compatibility. We had a very long discussion about this in OpenZFS because the other platforms were using C99 while we had backported everything to C89 on Linux because of the Linux kernel. No one could find a single example of ABI breakage caused by mixing and matching C89 and C99 (C99 LKM and C89 kernel). After a few years of not a single example being raised, the Linux team lead opted to adopt C99.
Now, there are flags affecting the ABI, but those are separate from the C standard version. As for C++, mixing standard versions does go badly because new language features require ABI changes.
>
>
>
next prev parent reply other threads:[~2018-09-18 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 15:37 [gentoo-dev] [RFC] C++ standard in ebuilds Guilherme Amadio
2018-09-17 16:40 ` Vadim A. Misbakh-Soloviov
2018-09-18 12:46 ` Richard Yao [this message]
2018-09-18 14:26 ` Guilherme Amadio
2018-09-17 17:24 ` Matt Turner
2018-09-17 18:38 ` Georg Rudoy
2018-09-18 14:31 ` Guilherme Amadio
2018-09-21 7:17 ` Dennis Schridde
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=812A3F5E-AA6A-4FFA-BF70-EE8B6565A6DF@gentoo.org \
--to=ryao@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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