To save C, we must save ABI

Re:To save C, we must save ABI by properparity on Sunday March 13, 2022 @11:51AM (#30662341)

C++ shouldn't be a problem? Just add a new namespace:

std::move_fast_and_break_things::vector

Or maybe the other way around so you can keep using std::vector: move_fast_and_break_things::std::vector

Then you can add a 'using namespace move_fast_and_break_things;' at the top of your files if you know you don't care about the ABI in your program.

[ Parent | on HN ]

Re:To save C, we must save ABI by brandmeyer on Sunday March 13, 2022 @02:47PM (#30664460)

You can do that with boost:: or absl:: right now. No need to involve the standards committee at all.

[ Parent | on HN ]

Re:To save C, we must save ABI by noobermin on Sunday March 13, 2022 @05:11PM (#30665749)

This doesn't just apply to stl, this also means breaking boost or w/e and you're stuck with the same problem, users are mad and pitted against library writers.

[ Parent | on HN ]

Re:To save C, we must save ABI by brandmeyer on Sunday March 13, 2022 @09:02PM (#30667413)

Boost doesn't even have a stable API commitment, let alone a stable ABI. Every release may require involvement from users to keep up to date.

Abseil doesn't even have releases any more. They expect you to live at head like GOOG does internally.

[ Parent | on HN ]

Re:To save C, we must save ABI by vlovich123 on Sunday March 13, 2022 @12:10PM (#30662587)

In c++ you do this with inline namespaces (change the default inline namespace version, keep the old one around, everything continues to work correctly in theory).

[ Parent | on HN ]

Re:To save C, we must save ABI by noobermin on Sunday March 13, 2022 @05:09PM (#30665737)

It's not just new and breaking things, it also applies to fixing bugs.

[ Parent | on HN ]