And when you do, you rattle the bells inside so it makes a ding.
And when you do, you rattle the bells inside so it makes a ding.
void main() {
//code
}
Is better than
void main()
{
//code
}
Why would you want to put it on a separate line? Are you paid by the height of the source file or something?
“Because fuck your sleep cycle that’s why”
I live in Vancouver and we’ve had massive issues with people (both tourists and locals) feeding coyotes in our downtown park. It got bad enough that they had to euthanize a bunch of coyotes because they were habituated to humans and have even attacked some people. They’re not puppers, they’re wild animals that play an important role in the ecosystem. You do them literally no favours by feeding them. Also, even worse, feeding bears.
Palestinian children: Stop bombing us
Israelis: Best we can do is silence
Remember how you used to have to go on sketchy piracy sites to install such sophicated spyware? Now it comes standard with every Windows installation! How convenient!
Freedom is not “being able to drive anywhere.” Freedom is being able to go anywhere with just your own body without a giant metal cage around it.
Both are usable, but I just don’t understand why you’d choose the separate line style if you were starting a new codebase. I can’t see the benefit of it, but that could also be me not having enough experience with the separate line style to see it’s advantages.
On the other hand, having the brace on the next line means that the parent statement and the code in the braces are further from each other, also more lines in the source file is more scrolling in general. You can fit less lines of code on the same vertical screen height if you have a lot of nested blocks or just generally use a lot of blocks. Especially for things like many small functions or many if blocks, being able to fit a few more on your screen is really convenient IMO.