4 ms·
>If the major version were to change, there wouldn't be any need for backward compatibility with the existing code, I have no idea where you get this idea from
by PaulDavisThe1st 8mo ago
>If the major version were to change, there wouldn't be any need for backward compatibility with the existing code,
I have no idea where you get this idea from. I expect gcc v28 to be able to compile C++ from 2008, and I'm not alone in that.
- maccard 8mo agoI completely agree with you. That said, I wish code written for gcc v28 didn't have to be binary compatible with C++ that was last compiled in 2008...
- PaulDavisThe1st 8mo agoIt isn't.
- maccard 8mo agoAnd yet GCC and MSVC both refuse to break ABI and have done so for over a decade.
- PaulDavisThe1st 8mo agoSome of us have been writing code for quite a bit longer than that. The 2000's and C++ were a clusterfuck largely for this very reason.
- maccard 7mo agoI’ve been writing c++ since before then too. A lot has changed in the world, notably package managers are actually used with c++ these days.
- gpderetta 7mo agoMSVC used to break library ABI pretty much on every release. They stopped after overwhelming customer demand.