3 ms·
That seems like a misconception about the driving forces behind C++ today.
by detaro 7y ago
That seems like a misconception about the driving forces behind C++ today.
- pjmlp 7y agoNot when one looks into the recent ABI discussions.
- gumby 7y agoYou mean a refusal to break ABI?
- pjmlp 7y agoYes, as means to achieve performance improvements that aren't that relevant to average Joe C++ dev. The one doing application stuff in Qt, MFC, wxWidgets. Or those like myself, where C++ only matters as means to implement native bindings to system libraries, or GPGPU shading languages based on C++.
- gumby 7y agoWell I can afford a complete ABI break (complete) given the kind of code I work on. Most people cannot. Binary incompatibilities are very hard for most people to manage. So I would benefit from any number of abi-breaking proposals but can understand the committees reticence.
- ptsneves 7y agoTo be honest it is hard to not break ABI. First you almost surely need to use PImpl and second hope a compiler upgrade keeps the standard library ABI compatible(eg ABI version flags in gcc). For a good look at how hard this is look at breakages in gentoo. This is basically the reason the greater open source community has their libraries in C: stable ABI, and consequently language bindings. Unless i am missing something big the concept of ABI stability in C++ is an art and requires a lot of discipline. At the top of my head only KDE was somehow successful but have a look at their guidelines[1]: again it requires a lot t of discipline. Also I believe that ABI compatibility with binaries compiled with different compilers also is complicated by things like name mangling conventions which are not common between compilers. There are so many things that can go wrong that the people i know that rely on ABI compatibility in C++ make a diff of their objdump output a ci test. Sometimes they get more paranoid and send me an assembly diff when they are suspicious(a compiler upgeade generated different jump prolog:) ). Ridiculous compared to the price of just running the compile again. The fact we control the whole machine's os image even makes it harder to understand... Oh man the pain I have... My apologies if my text is weird but proof reading in a phone is hard. [1]https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B https://community.kde.org/Policies/Binary_Compatibility_Issu...
- ptsneves 7y agoHmm got down voted. Would it be possible to elaborate on what is wrong with my post? Kind of new to HN so I would be glad to learn what I did wrong.
- gumby 7y agoPer HN's own guidelines your post did not deserve downvoting. Unfortunately some people do use downvoting to mean "I disagree", presumably based on the convention of some other forum. There's not much to be done about that except upvoting posts you see have been unfairly downvoted.
- deleted 7y ago[deleted]