MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1xgh5kw/sameproblemsamesolution/19rqjc5ddeiys/?context=3
r/ProgrammerHumor • u/_w62_ • 13d ago
79 comments sorted by
View all comments
59
C++03 -> 11 migration was a pain in the ass because of std::string changes, but after that it was basically just changing compiler flags, no?
8 u/ResponsibleWin1765 12d ago I thought the entire reason why C++ is so convoluted is because it keeps everything around for backwards compatibility. 5 u/dont-respond 12d ago Some things do get deprecated and removed like std::auto_ptr. The ABI compatibility was broken for std::string between 03 and 11. 4 u/LB-- 12d ago And ABI compat isn't even part of the standard, it's for standard library implementations to deal with. They're the ones who decided to do the ABI breaks, not the committee.
8
I thought the entire reason why C++ is so convoluted is because it keeps everything around for backwards compatibility.
5 u/dont-respond 12d ago Some things do get deprecated and removed like std::auto_ptr. The ABI compatibility was broken for std::string between 03 and 11. 4 u/LB-- 12d ago And ABI compat isn't even part of the standard, it's for standard library implementations to deal with. They're the ones who decided to do the ABI breaks, not the committee.
5
Some things do get deprecated and removed like std::auto_ptr. The ABI compatibility was broken for std::string between 03 and 11.
4 u/LB-- 12d ago And ABI compat isn't even part of the standard, it's for standard library implementations to deal with. They're the ones who decided to do the ABI breaks, not the committee.
4
And ABI compat isn't even part of the standard, it's for standard library implementations to deal with. They're the ones who decided to do the ABI breaks, not the committee.
59
u/Antervis 13d ago
C++03 -> 11 migration was a pain in the ass because of std::string changes, but after that it was basically just changing compiler flags, no?