unbrace

A 4' long unbraced 2x6 is rated at 4247 lbs in the page you linked.

The unbraced if is still not great style, but it wasn't the cause of the security blunder.

With all the pitfalls of C, the unbraced ifs feels like a very impotent example.

It's funny because there is an unbraced if and a goto, but the error is sonewhere else

It shouldn't have let me screw up. If only we had a new language without unbraced-ifs ... and it somehow caught on and replaced all 40-years of legacy C code.

I keep one-line blocks unbraced when possible and my reasoning is definitely not to feel like a tough macho man.

I want to know why you copied something as simultaneously horrendous and useless as unbraced blocks?

If you think someone is "woefully negligent at their job" for modifying an unbraced if statement, how about pilots who fly their airliner into the ground?

Make sure it's a one line block that is totally unbraced with only single letter variable names if you do it because otherwise it's just faux-macho C and that's /weak/.

"I don't see unbraced-ifs as this great security flaw, and I don't see 'fixing' it as curing some endemic problem with language design that's going to lead us to not have bugs like this again.

> Make sure it's a one line block that is totally unbraced with only single letter variable names if you do it because otherwise it's just faux-macho C and that's /weak/.I think you're projecting.

In addition, this is just another unsafe macro which could be made safe as above.#4 doesn't explain the solution to the problem it poses which is annoying because it's the most important one IMO. There are a number of ways to make a multi-line macro safe for use in an unbraced expression body.

Apple's goto-related SSL vulnerability this week is a blatant, high-profile reminder of how harmful unbraced conditionals are.