> That's exactly the kind of thing that the boosters of all those previous efforts said. But somehow it never quite worked out. No, they really didn't. Let's r

> That's exactly the kind of thing that the boosters of all those previous efforts said. But somehow it never quite worked out. No, they really didn't. Let's review some of the big cases. - SafeC: not based on a mainstream C compiler, so can't handle gcc/clang extensions (Fil-C can). Had no story for threads or shared memory (Fil-C does). Hence, not really compatible. - CCured: incompatible (cannot compile C code with it without making changes, or running their tool that tries to automate the changes - but even then, common C idioms like unions don't quite work). Didn't use a major C compiler, - SoftBound: not totally memory safe (no attempt to provide safety for linking or function calls). But at least it's highly compatible. I can list more examples. Fil-C is the first to get both compatibility and safety right.