this post was submitted on 17 Jun 2023
23 points (100.0% liked)

Programmer Humor

32371 readers
559 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 1 year ago (2 children)

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.

[–] [email protected] 2 points 1 year ago (1 children)

It goes on the line! If you put it below, you're wasting a line for no extra readability!

[–] [email protected] 3 points 1 year ago (1 children)

It goes on the next line, so you can have open and close brackets at the same indent depth for easy visual matching.

[–] [email protected] 1 points 1 year ago (1 children)

Your closing } goes on a new line below at the same indent depth as the line containing the open {!

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)
fn main() {
    println!("WTF?");
          }

PS: I know what you meant

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

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. ;)

[–] [email protected] 1 points 1 year ago

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 😜