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.
Post History
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 -- u...
#3: Post edited
by
klutt
·
2020-10-31T01:37:47Z (over 3 years ago)
- 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 need 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.- 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?
- 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?
#2: Post edited
by
Moshi
·
2020-10-30T22:06:51Z (over 3 years ago)
This question is pretty much the same for any programming language that uses braces, therefore [language-agnostic]
#1: Initial revision
by
klutt
·
2020-10-30T15:00:43Z (over 3 years ago)
Is omitting braces for single statements bad practice?
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 need 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.
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?