On Monday, 10 April 2017 at 23:33:17 UTC, Walter Bright wrote:
On 4/10/2017 6:08 AM, Matthias Klumpp wrote:
I also want to stress that having a single C++ library like
Boost compiled into
stuff and rolling dependency transitions when its API/ABI
changes with a major
release is less of a problem than having the entire language
give zero stability
and interoperability guarantees on anything that is compiled
with it.
How is the g++/clang++ issue handled?
The C ABI is 100% compatible, the C++ ABI is "mostly" compatible,
there is some deliberate breakage from the Clang guys though.
The issue isn't actually handled in Debian as all our code is
always compiled with GCC, I am not aware of anything defaulting
to Clang (although it might exist, but definitely not for library
packages).
With only one dominant compiler, things are way easier ^^
