News for hackers. Stuff that matters.
Re:The Evolution of C Programming Practices: A Study of Unix... by vardump on Friday May 11, 2018 @01:47PM (#17049367)
Boilerplate doesn't mean (binary) bloat.
Re:The Evolution of C Programming Practices: A Study of Unix... by WalterBright on Friday May 11, 2018 @02:11PM (#17049570)
Rather than debate, here's an example of replacing goto's with a nested function:

https://github.com/dlang/dmd/pull/6656/files

Re:The Evolution of C Programming Practices: A Study of Unix... by vardump on Friday May 11, 2018 @02:49PM (#17049877)
I guess it's a matter of taste, but I often (not always) prefer less return statements in a function with gotos to error handling/cleanup code. Especially in kernel mode drivers.
Re:The Evolution of C Programming Practices: A Study of Unix... by WalterBright on Friday May 11, 2018 @02:56PM (#17049944)
Check the asm code generated by your compiler - it may optimize multiple returns into one.
Re:The Evolution of C Programming Practices: A Study of Unix... by vardump on Friday May 11, 2018 @05:06PM (#17050806)
Not performance or code size I'm concerned, it's mainly about correctness. Stuff like input validation and releasing a spinlock in kernel code.