Git's list of banned C functions

Re:Git's list of banned C functions by brmgb on Thursday March 04, 2021 @06:42PM (#26350142)

The issue is pretending that C even has strings as a semantic concept. It just doesn't. C has sugar to obtain a contiguous block of memory storing a set number of bytes and to initialize them with values you can understand as the string you want. Then you are passing a memory address around and hoping the magic value byte is where it should be.

C is semantically so poor, I find it hard to understand why people use it for new projects today. C++ is over complicated but at least you can find a good subset of it.

[ Parent | on HN ]

Re:Git's list of banned C functions by anikom15 on Friday March 05, 2021 @01:12AM (#26353424)

C is a good language for solo projects because of it’s simplicity. By simplicity, I mean understanding what it’s doing under the hood. ‘Portable assembly’ is not an unfitting title.

Big C projects work well when they are carefully maintained (like Git).

[ Parent | on HN ]

Re:Git's list of banned C functions by akira2501 on Friday March 05, 2021 @01:55AM (#26353687)

> but at least you can find a good subset of it.

It's a constantly shifting subset, though. Moving slowly is a feature of C for some.

[ Parent | on HN ]

Re:Git's list of banned C functions by account42 on Friday March 05, 2021 @07:59AM (#26356343)

You can pick a subset of C++ now and it will not be worse in the future. There may be better ways to do things added but that seems a weird thing to complain about and you can just ignore it if you want.

[ Parent | on HN ]