Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Is omitting braces for single statements bad practice?

Post

Is omitting braces for single statements bad practice?

+9
−4

Consider this code:

while(arr[index] != 0)
    index++;

vs

while(arr[index] != 0) {
    index++;
}

Personally, I prefer the first. The fact that the braces are not needed makes them -- unnecessary. :)

To me, it's just clutter that wastes a line. Or 2 if you're one of them that also want the opening brace on a new line. The line waste can be avoided though, if you do like this:

while(arr[index] != 0) index++;

I often do that, and I like the style. Partially because it makes those loops stand out from loops with braces.

One argument I've heard for always using braces is that if you want to add another statement, then you need to remember adding braces or you will have bugs that can be hard to find. For instance, this would be an endless loop:

while(arr[index] != 0) 
    println("No zero found");
    index++;

While this is technically true that this mistake can be done, I find it a bit meh as an argument. If you're using an editor that autoindents the code, this mistake would be spotted immediately. And since using such an editor is something that you should do anyway, the point of this argument is a bit moot.

Plus, even though I have often coded without such an editor, I cannot remember ever doing that mistake. It feels like a mistake that one could do if you're used to Python. But adjusting coding standards of C, C++, Java and such to not confuse Python coders does not really seem like the right path to go.

Apart from this argument, I have not really seen anything else than the consistency argument. That always using the same style is consistent. Well it's true, but consistency is not ALWAYS good.

Have I missed something here? What do you say? Is omitting braces for single statements bad practice?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

Put the `{` on the next line and you wouldn't waste any lines. (1 comment)
General comments (5 comments)
General comments

With full-feature IDEs becoming common-place you might think the argument for always-braces is weakened. I'm not so sure. However, the legendary goto fail bug still looms as a mammoth counterexample. One assumes that Apple's developers used a full-featured IDE and still this mistake happened. With braces it would have been much harder to make that mistake. But not impossible!

klutt‭ wrote over 3 years ago

While that example is pretty interesting, it's anecdotal evidence. I understand that it's still possible to produce bugs like this. One could also reasonably argue that it could have been avoided if they used else if instead of if or didn't use goto.

klutt‭ wrote over 3 years ago

To me it sounds a bit like "you should not use i and j as counters in a nested for loop, because you CAN use the wrong one by accident" ;)

Lundin‭ wrote over 3 years ago

If you enforce a style that always uses braces you can check it with static analysis tools though. Unlike using the wrong variable and similar application level bugs.

jrh‭ wrote over 3 years ago · edited over 3 years ago

I've heard the "we don't need to do this anymore because modern editors are wonderful" argument a bunch of times, but I've found that these editors struggle in C++ with hokey macros, build scripts that set include directories that the IDE can't understand, and other weird tricks like that. Combine all that and my "modern IDE" isn't much better than Notepad++ and is filled with red squiggles and false positives and it takes about 10 seconds worth of idle time to parse the code.