Ah yes, the use of goto conjures up the 800-year-old essay in the room.
The way they use it is widely understood and accepted in C error handling. It's also not the only way you can screw up, either, which is a good reason why you should add a static analyser to your build process.
Comments
All that text, so many points, and somehow the author managed to avoid the 800-pound gorilla in the room: the use of goto.
Ah yes, the use of goto conjures up the 800-year-old essay in the room.
The way they use it is widely understood and accepted in C error handling. It's also not the only way you can screw up, either, which is a good reason why you should add a static analyser to your build process.
goto in C is perfectly fine in this sort of situation. Its the only way to do sane error handling.
That is because C is not a good language.
Don't get be wrong, it's the best language for the space that it occupies. There is no better language to implement such things.
But it still isn't good. It's just that it's failed to be replaced by anything better.