C / C++ are very good languages in all sorts of ways. However, there are components that currently have... flaws. This being one of them. As such, I complain about said flaws, in the hopes that someone will take notice, and/or someone will point me in the direction of things that contain the good parts of C / C++ without said flaws.
I have already learned a fair bit about bounds checking, SIMD instructions, etc, etc from this. And I always want to know more.
*
And no, it is the same problem. Namely, that the memory models of C and C++ doesn't match with the underlying hardware, and the mismatch is such that things that are trivial to do on the underlying hardware are literally impossible to do with C and C++.
Part of this is for compatibility purposes, but there are ways to keep the compatibility that don't present this sort of problem.
C / C++ are very good languages in all sorts of ways. However, there are components that currently have... flaws. This being one of them. As such, I complain about said flaws, in the hopes that someone will take notice, and/or someone will point me in the direction of things that contain the good parts of C / C++ without said flaws.
I have already learned a fair bit about bounds checking, SIMD instructions, etc, etc from this. And I always want to know more.
*
And no, it is the same problem. Namely, that the memory models of C and C++ doesn't match with the underlying hardware, and the mismatch is such that things that are trivial to do on the underlying hardware are literally impossible to do with C and C++.
Part of this is for compatibility purposes, but there are ways to keep the compatibility that don't present this sort of problem.