upvote
Fil-C is also a great solution, albeit with different performance trade-offs.
reply
In theory, scpptool provides another solution with different performance, compatibility and portability trade-offs. Unlike Fil-C, it is not "fanatically compatible" with existing C code. But in theory, with maybe some minor adjustments to the code (and maybe less-minor adjustments to the build system), you can auto-translate your existing C code base to an essentially memory-safe subset of C++ at build-time [1].

While generally more of a hassle than Fil-C, the scpptool approach provides an incremental path to optimal performance (for performance-sensitive sections of the code) via migration to a (statically-enforced) memory-safe subset of C++. And unlike Fil-C, the scpptool solution essentially maintains the portability of the original code, as well as its deterministic performance and resource usage (i.e. no GC). It also supports ABI compatibility via "unsafe"/"check-suppression" annotations. The scpptool approach is not so much an alternative to Fil-C, as it is an optional path forward for C (or C++) code bases that may (or may not) be already using Fil-C for memory safety.

[1] https://github.com/duneroadrunner/SaferCPlusPlus-AutoTransla...

reply
What good is a car that goes 1000 miles per hour if it has no brakes?

It's time for performance above everything else to die, especially on anything and everything that gets anywhere close to untrusted data.

reply
Same, made a fil-c fork of nginx a while back, saved me from many RCEs https://github.com/remixer-dec/filc-nginx Don't have the tokens to maintain it though :(
reply
This sounds like a fantastic solution, especially for non-high-volume stuff. Would you consider writing down your setup and experiences? I'm sure it'll be a hit on this site!
reply
fv?
reply
Formal verification.
reply
formal verification?
reply