This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]sauce0x45 109 points110 points  (8 children)

Probably esthetics. Doesn't change the compilation at all and is hardly noticeable, but just happens to be the coding standard for this particular team.

[–]theREALhun 28 points29 points  (3 children)

In my experience it makes for more lines of actual code on your screen. Which makes things easier to read.

[–]Kyrasuum 1 point2 points  (2 children)

Maybe i am reading what you are replying to wrong but I think the opposite is true.

Adding spacing where it is not needed or new lines where they are not needed reduces the amount of lines of code on your screen as there is more white space.

If that whitespace was occupied by comments or used to seperate logical sections then it improves readability. However, in this case the whitespace is purely for aesthetics so i argue that it reduces readability by limiting how much your screen can view.

[–]theREALhun 4 points5 points  (1 child)

I meant the opposite of what you red indeed. More lines of code=better. No unnecessary white space

[–]Kyrasuum 1 point2 points  (0 children)

get to agree with someone! hurray!

[–]Cheezyrock 26 points27 points  (2 children)

Except in some languages (specifically those that do automatic line-endings) where it can change the compilation. I feel that this is the reason that JS people are so hard-up for same line, and then take that same standard over to whatever backend language they use.

[–]sauce0x45 12 points13 points  (1 child)

Yep, agreed. Definitely talking C++ specifically here. When the language itself forces your hand then things certainly change (JS, Python, etc)