[drivingmenuts]

I use 120 or 132 (no idea why I picked that number), but I tend to break my lines well before that, especially on function signatures.

I'm that git that puts each param on a separate line (so I can quickly comment them out when I need to). It annoys other programmers, but once I explain why ...

They're still annoyed, but at least they're quiet about it.

[SoftTalker]

Some old "dumb" terminals could be switched into 132-column mode, this corresponded to the 132 columns on the line printers that printed on wide fan-fold green-bar paper.

The 80 column standard for a line of code goes back to the 80 columns on a standard IBM punch card. Why 80 columns on a punch card? I don't know that one.

[bitwize]

If you're that git that makes one param per line a standard that you can flunk code review for not adhering to, I'd seriously consider switching jobs were I under you.

[beeflet]

I will do this, but only if it has many parameters.

It makes it easier to visually parse the function name, templates, outputs, etc. from the parameters than if they were all on one line

[qayxc]

> I'm that git that puts each param on a separate line

I do that too :)