4 ms·
Maybe dropping compatibility with C is a good thing? All other languages wanting to interface with C seem to be using libffi or something. Currently C++ gets
by ericfrederich 9y ago
Maybe dropping compatibility with C is a good thing?
All other languages wanting to interface with C seem to be using libffi or something. Currently C++ gets a shortcut, but in the future maybe it could go through an FFI.
It'd still be compatible with C from libraries, just not source. Those libraries would have to ship header files free of macros of course.
- devwastaken 9y agoI think you're advocating for dropping compatability with a little under half of all c++ projects.
- nachexnachex 9y agoI don't see how losing backwards compatibility would be a good thing per se. Even if the preprocessor were considered a problem (which is disputed), it could coexist with a new FFI system that could be implemented. Losing backwards compatibility is usually a price to pay, not an objective. As an example, Python 3k chose to lose partial compatibility to 2.7 in order to change some parts of the language. While the user and maintainer community still debates if the change itself was a good decision (a different discussion IMO...), probably most will agree that the incompatibility bit has been and will be for some time a source of pain.