Subject: Re: [boost] ABI issues with -std
From: degski (degski_at_[hidden])
Date: 2018-08-20 12:46:37
On Mon, 20 Aug 2018 at 15:08, Gavin Lambert via Boost <boost_at_[hidden]>
> Yes, there are a lot more things that can cause the exact same problem
> -- this is one of the reasons why the Windows builds include so many
> different "ABI altering" flags in their names.
Yes MS worries a lot more about breaking ABI's, as there are billions of
computers running the thing, so you have to jump through hoops, to work
around those issues (which is just another word for "hacking").
Historically Linux hasn't had to worry about this as much since
> "everything" is compiled from source using the same compilers and
> libraries -- except when they aren't.
See above, and up till now there haven't been many std's either (C++03 is
just some gloss over of C++98), so there was nothing to worry about. The
implicit assumption is obviously that not only is all compiled from source,
but everything is compiled with the same std and compiler, as no-one in his
right mind would compile one bit with C++03 and another bit with C++17 (if
you're compiling all from source). What does not help is that nothing until
C++14 (maybe even in C++11) was ever removed from the std, so this is also
a novelty, all of a sudden C++14 doesn't compile C++03 code (which I would
say has always been another implicit assumption).
-- *âIf something cannot go on forever, it will stop" - Herbert Stein* *âNo, it isnât truth. Truth isnât truth" - Rudolph W. L. Giuliani*