News for hackers. Stuff that matters.
Re:22nd Century C by microcolonel on Sunday September 11, 2016 @12:08AM (#12471952)
The "case" and "default" overrides seem kinda dicey.
Re:22nd Century C by Tim61 on Sunday September 11, 2016 @01:59AM (#12472185)
Yeah, that is probably what bothers me the most about this. I write C code almost everyday. I can't remember the last time I forgot a "break", but I do use fallthrough when it simplifies the logic. It also breaks even the simple case of having multiple labels for the same code.

Also, the for-loop overrides are ugly and pointless, IMO.

Re:22nd Century C by jonathankoren on Sunday September 11, 2016 @03:59AM (#12472442)
Yup. Congratulations kid. You broke fall-through, perhaps the biggest advantage of a switch over else-ifs.
Re:22nd Century C by abecedarius on Sunday September 11, 2016 @11:32AM (#12473846)
I defined the same macros but with different names, back when I still coded in C. I still think it's a good idea which tends to get reactions like "Ew! Wash your hands."