Re:C but Safe
by jmull on Thursday April 04, 2024 @08:05PM
(#39937318)
The problem with black-and-white thinking is that it's too simplistic to apply to the great majority of real-world problems.
Safe C provides an incremental migration path from unsafe C to safe C. And you don't need to completely rewrite, but instead address the issues flagged, which will often be a lot less work and risk than an actual rewrite in a new language. (This seems obvious to me, but apparently not?)
Re:C but Safe
by betz47 on Friday April 05, 2024 @05:33AM
(#39940454)
This is our thinking as well, a complete rewrite in another language (short of formally verifying the code) could introduce all sorts of logical bugs that did not exist or were patched in the old code.
Safe C provides an incremental migration path from unsafe C to safe C. And you don't need to completely rewrite, but instead address the issues flagged, which will often be a lot less work and risk than an actual rewrite in a new language. (This seems obvious to me, but apparently not?)