3 ms·
Eh. Good C programmers know what's safe and what's not. Often comments call out sketchy stuff. Just because it's not a language keyword, doesnt mean it's not
by chillingeffect 2y ago
Eh. Good C programmers know what's safe and what's not. Often comments call out sketchy stuff. Just because it's not a language keyword, doesnt mean it's not called out.
Bad C programmers though? Their stuff is more dangerous and they don't know when and don't call it out and should probably stick to Rust.
- sunshowers 2y agoNo, it's been proven over and over that simply knowing invariants is not enough, in long-term projects built by large teams where team members change over time. Even the most experienced C developers are going to fail every so often. You need tooling that automates those invariants, and you need that tooling to fail closed. I take a hard line on this stuff because we can either keep repeating the fundamental mistake of believing things like "willpower" to write correct code are real, or we can move on and adopt better tooling.
- fasterthanlime 2y agoTrue! Only, Good C programmers don’t exist.
- hyperbrainer 2y agoAnd where can I find this mythical "Good C programmer"?
- 12_throw_away 2y agoDunno why this is being downvoted, obviously no true Scotsman would ever use memory after freeing it.