this post was submitted on 17 Jun 2023
95 points (100.0% liked)
Programmer Humor
32503 readers
402 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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 {!
PS: I know what you meant
This, as it also helps when using % to go to the matching open/close bracket when the cursos doesn't jump all around the place..
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.
That is, unless the font used messes it up. ;)
That’s horrible.
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 😜
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.