News for hackers. Stuff that matters.
Re:Bzip2 crate switches from C to 100% rust by quotemstr on Wednesday June 18, 2025 @12:14AM (#44306601)
C++ binaries should be doing the same. Externally, speak C ABI. Internally, statically link Rust stdlib or C++ stdlib.
Re:Bzip2 crate switches from C to 100% rust by pjmlp on Wednesday June 18, 2025 @04:02AM (#44307666)
OWL, MFC, Qt, VCL, FireMonkey, AppFramework, PowerPlant...

Plenty do not, especially on Apple and Microsoft platforms because they always favoured other approaches to bare bones UNIX support on their dynamic linkers, and C++ compilers.

Re:Bzip2 crate switches from C to 100% rust by pjc50 on Wednesday June 18, 2025 @04:48AM (#44307968)
Exporting a C API from a C++ project to consume in another C++ project is really painful. This is how you get COM.

(which actually slightly pre-dates C++, I think?)

Re:Bzip2 crate switches from C to 100% rust by Someone on Wednesday June 18, 2025 @09:48AM (#44309861)
> This is how you get COM. (which actually slightly pre-dates C++, I think?)

No. C++ is from 1985 (https://en.wikipedia.org/wiki/C%2B%2B), COM from 1993 (https://en.wikipedia.org/wiki/Component_Object_Model)

Re:Bzip2 crate switches from C to 100% rust by quotemstr on Wednesday June 18, 2025 @11:30AM (#44310774)
COM is actually good though. Or if you want another object system, you can go with GObject, which works fine with Rust, C-+, Python, JavaScript, and tons of other things.