3 ms·
You wouldn't - you'd write it in the safe C subset? Presumably it's easier to rewrite part of your app rather than the whole thing. But I'm all for a safe ver
by musicale 3y ago
You wouldn't - you'd write it in the safe C subset?
Presumably it's easier to rewrite part of your app rather than the whole thing.
But I'm all for a safe version of C17 (or C23/24). It's so disappointing that there isn't a standard memory-safe compiler/runtime/ABI. (And while they're at it, the stack should grow up rather than down.)
Perhaps CHERI or similar will catch on someday. Maybe Apple could try implementing memory checking for clang and Apple Silicon.
- uecker 3y agoI am currently working on a GCC frontend that has a memory safe mode where it would warn about every unsafe constructs. At the same time a trying on modifying some of my projects to work with it. To me, this seems an entirely reasonable approach. But it is a spare time project, so progressing slowly.