News for hackers. Stuff that matters.

A comment on Git's list of banned C functions. Parent comment

Re:Git's list of banned C functions by kaba0 on Friday March 05, 2021 @11:10AM (#26358403)
Compile time security measures have absolutely no runtime overhead. Also, I don’t see what you mean by File::open — there is a kernel call somewhere there. But if you are writing a new OS you are free to implement the fopen call as you wish - C has no advantage here.
[ Parent | on HN ]
Re:Git's list of banned C functions by IgorPartola on Friday March 05, 2021 @05:13PM (#26362841)
Not all bounds checking can be done at compile time, can it? You can’t check if a file exists on a target system before it is opened at compile time, can you?
[ Parent | on HN ]