News for hackers. Stuff that matters.
Re:C++26 Disapproved by charcircuit on Wednesday November 04, 2026 @12:54AM (#50361905)
Who cares about the ABI when the current ABI has a bunch of bad issues with it. For any backwards compatibility thing there is always AI that can rewrite old code.
Re:C++26 Disapproved by NekkoDroid on Wednesday November 04, 2026 @03:52AM (#50362943)
The compiler vendors care. It is also the reason why C++ never actually had a GC, even if the standard had it specified (and removed it with C++23).
Re:C++26 Disapproved by bluGill on Wednesday November 04, 2026 @08:07AM (#50365033)
ABI isn't just what rewriting code. Even if you rewrite the code, you still have to test it, certify it, and so on. Because C++ has an ABI, I mix code that is already built with new code and only recertify my new code.

It is a huge pain, and quite honestly, most of the reasons I have to maintain ABI are political and thus not up for a technical discussion, but I still have to do it.

Re:C++26 Disapproved by charcircuit on Wednesday November 04, 2026 @12:50PM (#50369084)
You can make linking against different abi not allowed. And all the stuff you are complaining about can be handled in <24h by an AI agent.