News for hackers. Stuff that matters.
Re:fork() can fail by cperciva on Wednesday August 20, 2014 @04:32PM (#8204427)
You mean, after exit(0) returns?
Re:fork() can fail by AnimalMuppet on Wednesday August 20, 2014 @05:07PM (#8204635)
Not after exit(0) returns, no. Instead, you're going to want it after some programmer removes exit(0) six months from now.
Re:fork() can fail by hamburglar on Wednesday August 20, 2014 @08:10PM (#8205346)
smart-ass comment: you should put two breaks in for when some programmer removes one of them six months from now. ;)

edit: i know it's not totally analogous since removing the exit and not noticing there's no break is a lot more likely than just randomly removing a break, but the "let's prevent someone clumsy from screwing this code up in the future" argument always makes me laugh a little.

Re:fork() can fail by AnimalMuppet on Friday August 22, 2014 @12:38PM (#8212812)
Of course, you can always take it too far. Two breaks is too far, obviously (I'm pretty sure you agree with me on that).

Is a break after an exit too far? It may well be, but it's less clearly too far than two breaks are.

Re:fork() can fail by loup-vaillant on Wednesday August 20, 2014 @06:05PM (#8204926)
I'm going to write a pre-processor which adds the appropriate `break` statements automatically. No more fall-through bug.

(And if you really want to fall through, I could add a `fallthrough` keyword.)

Re:fork() can fail by cperciva on Wednesday August 20, 2014 @06:13PM (#8204965)
For what it's worth, it's a style bug in FreeBSD to have a fallthrough which does not have a /* FALLTHROUGH */ comment.
Re:fork() can fail by scintill76 on Wednesday August 20, 2014 @10:04PM (#8205640)
Yep, could even re-use the "continue" keyword.