4 ms·
They do. ABI breaking changes are routinely voted down unless they are really worth it (and the only non backward compatible change that was accepted that I'm a
by gpderetta 7y ago
They do. ABI breaking changes are routinely voted down unless they are really worth it (and the only non backward compatible change that was accepted that I'm aware is the std string changes in C++11).
- Ididntdothis 7y agoMaybe things are better now but in the past almost every new library I added to my projects required a lot of fiddling with headers , link options and other stuff. With C# this is so easy in comparison.
- steveklabnik 7y agoThis paper is related and interesting: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1863r0.pdf http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p186...
- Scramblejams 7y agoThanks for the link, a good read. As somebody who kicks C++'s tires once in a while and is always put off by the incredible complexity of the language, and the complexity and friction and fragility of its workflow, I was sad not to see any explicit mention of pairing an ABI break with removal of the bad parts. (Yeah, I know, that might mean source-level backwards incompatibility...) Makes me wonder if it's ever even discussed at a high level.