Totally agree, all my { end up on the next line, 1st spot when starting a function, last character of the keyword when starting an if/for/… section. I even put the closing one on the same line when it’s single line, else either at the end of the closing line (when changing really old code) or same indent.
So indenting varies a lot, which makes most ‘new’ programmers go mental.
while (my code)
{ I'lldo it my way }
if (! liked)
{ toughen-up }
else
{ get used to it
multi-line can go both ways...
}
To be honest, I think the forced ‘fixed’ indent in python is horrible, not being able to identify the different block function just by the indent, not being able to use % in vi to find the correct end,…
Much be an age thing, I learned to program in the 80s.
The { of the else is just the 2nd, optional, part of the if statement, so I was learned to align it with the opening keyword. I do the same with the then keyword, when the language requires a then, then it’s aligned with the i if if an the { with the f of if.
In the old days, when memory was expensive (in the day of 4k computers), even an extra cr/lf was worth preventing. Hence C has no then, C layout is usually { … } for one liners… or even without the { },… I learned to program in the IT dark ages. ;)
Is this some kind of python meme I’m too C++ to understand?
Now, I’m completely willing to start a war about { going on the next line.
It goes on the line! If you put it below, you’re wasting a line for no extra readability!
It goes on the next line, so you can have open and close brackets at the same indent depth for easy visual matching.
Your closing } goes on a new line below at the same indent depth as the line containing the open {!
fn main() { println!("WTF?"); }PS: I know what you meant
Totally agree, all my { end up on the next line, 1st spot when starting a function, last character of the keyword when starting an if/for/… section. I even put the closing one on the same line when it’s single line, else either at the end of the closing line (when changing really old code) or same indent.
So indenting varies a lot, which makes most ‘new’ programmers go mental.
while (my code) { I'll do it my way } if (! liked) { toughen-up } else { get used to it multi-line can go both ways... }That is, unless the font used messes it up. ;)
That’s horrible.
To be honest, I think the forced ‘fixed’ indent in python is horrible, not being able to identify the different block function just by the indent, not being able to use % in vi to find the correct end,…
Much be an age thing, I learned to program in the 80s.
Why isn’t the else curly lined up with the end of the else word? I’d your gonna go crazy might as well go all the way I guess 😜
The { of the else is just the 2nd, optional, part of the if statement, so I was learned to align it with the opening keyword. I do the same with the then keyword, when the language requires a then, then it’s aligned with the i if if an the { with the f of if.
In the old days, when memory was expensive (in the day of 4k computers), even an extra cr/lf was worth preventing. Hence C has no then, C layout is usually { … } for one liners… or even without the { },… I learned to program in the IT dark ages. ;)
Wonder what the x-axis is? Survey year? Years of experience? Caffeine intake?
Anyway, I can hardly join a holy war – I code in assembly most comfortably, which I’m pretty sure is heresy these days.