30% safer, 30% more readable, and 30% more productive would be even better.
> When was the last time you did “cut your arm” with goto specifically?
It's been a while since I've used C, and even longer since I've personally written goto statements. I do remember frequently getting tripped up on them right after undergrad. It's not friendly, and I don't ever wish to touch them again.
I'm working in a C++ game engine project right now and it's constantly segfaulting. I can't imagine that setting register jumps manually in complex higher level code would improve my situation.
When I get to choose the language, I use Rust. It fits the C use case and fixes many of the warts.
I do remember frequently getting tripped up on them right after undergrad. It's not friendly, and I don't ever wish to touch them again.
So it’s something bad from the undergrad past, no details. Must we take an advice based on that? I’m not sure I will.
I'm working in a C++ game engine project right now and it's constantly segfaulting. I can't imagine that setting register jumps manually in complex higher level code would improve my situation.
Neither would tabooing something based on weak or no evidence. “It doesn’t help here” and “we ban it and ostracize its use” are two different claims.
Even 30% safer is a win.
30% safer, 30% more readable, and 30% more productive would be even better.
> When was the last time you did “cut your arm” with goto specifically?
It's been a while since I've used C, and even longer since I've personally written goto statements. I do remember frequently getting tripped up on them right after undergrad. It's not friendly, and I don't ever wish to touch them again.
I'm working in a C++ game engine project right now and it's constantly segfaulting. I can't imagine that setting register jumps manually in complex higher level code would improve my situation.
When I get to choose the language, I use Rust. It fits the C use case and fixes many of the warts.