3 ms·
Breaking compatibility is mandatory; otherwise Haiku would be stuck with its C++98 API. Trying to interface otherwise-modern code with the vintage BeOS API is d
by MrMorden 9y ago
Breaking compatibility is mandatory; otherwise Haiku would be stuck with its C++98 API. Trying to interface otherwise-modern code with the vintage BeOS API is doable but does not exactly lead to rising property values in Tokyo.
- waddlesplash 9y agoWell, we are still stuck with a C++98 API... some parts of the x86_64 core code in the kernel, since that's only ever compiled with GCC5+ use C++11, but by and large we're still C++98. (The Be API used almost none of the STL, so it doesn't really make a massive amount of difference to us. <functional> would be of use in event handling code, as well as a few other new language keywords and the like, but by and large we'd be unaffected.)