Code style discussion

So we have style on the same line:1|try {
2| foo();
3|} catch(FooFuckedUpExeption) {
4| bar();
5|}And we have brackets on their own line:1|try
2|{
3| foo();
4|}
5|catch(FooFuckedUpExeption)
6|{
7| bar();
8|}So when you read line 1 of te first one, you know line 1 opens a try block.
Now what does line 1 of the second style do?line 1 a try
line 2 opens blockWhy woud you use the second style? It's just confusing.
Another example: if (foo) {
bar();
} else {
fizz();
}
if (buzz) {
fizzbuzz();
}

if (foo)
{
bar();
}
else
{
fizz();
}
if (buzz)
{
fizzbuzz();
}You can see in the first style where the first if else logic stops and the second if begins, in the second style this is less clear so you need another newline for readability.

Can we discuss this shit? I'll try to remain civil when i prove newliners wrong.

Attached: python was right using indent as syntax.png (218x483, 7K)

Other urls found in this thread:

kernel.org/doc/html/v4.10/process/coding-style.html
twitter.com/NSFWRedditImage

your shit in unreadable . Go eliminate yourself

I'm laughing uncontrollably

I didn't expect my multi line code blocks to be inline...

Attempt 2

So we have style on the same line:
1|try {
2| foo();
3|} catch(FooFuckedUpExeption) {
4| bar();
5|}

And we have brackets on their own line:

1|try
2|{
3| foo();
4|}
5|catch(FooFuckedUpExeption)
6|{
7| bar();
8|}

So when you read line 1 of te first one, you know line 1 opens a try block.
Now what does line 1 of the second style do?
line 1 a try
line 2 opens block
Why woud you use the second style? It's just confusing.
Another example:

if (foo) {
bar();
} else {
fizz();
}
if (buzz) {
fizzbuzz();
}

if (foo)
{
bar();
}
else
{
fizz();
}
if (buzz)
{
fizzbuzz();
}

You can see in the first style where the first if else logic stops and the second if begins, in the second style this is less clear so you need another newline for readability.

Can we discuss this shit? I'll try to remain civil when i prove newliners wrong.

>python code monkey

I prefer:
if
(
foo
)
{
bar
()
;
}
else
if
(
fizz
)
{
buzz
()
;
}

for maximum readability

either that or:
if
(
foo
) { bar
(); }
else
if (fizz
) {
buzz
()
;}

In the first one, you cannot easily tell where the block ends. In the second one, you put your cursor on the openning bracket, then scroll down until you meet the end bracket. It's clearer, especially when you have nested brackets.

The answer to anything involving braces is follow whichever is the standard for the given language you're working with or the company you're working for. In JavaScript it's standard to put opening braces on the same line as the statement and use 2 spaces for indentation, while in C# it's expected to put braces on newlines and use 4-space indentation. If the given language doesn't have any preferences, just use whichever you want as long as you keep it consistent throughout the codebase.

Here, let me show you the language of practical syntax.
(if foo
'bar
'baz)

If you have one curly bracket on the same line as the declaration, why not have the closing one inline too?
And what do you actually need multiple types of brackets for? The evaluation can always follow the same rules so a distinction isn't really necessary.
And why would you have semicolons at the end of every line of code?