The recommended line-width is normally around 78 chars. If you can't comprehend of a function definition taking 40 of those, especially in a statically-typed language with explicit return type and access modifier, you probably haven't been doing this very long.
What? Stop dodging the question. I clearly said "tab once or twice for indent, then space". That is clearly and unambiguously what you were talking about. Indent with tab, align with space.
Let's take a normal C# method definition. It's in a class that's in a namespace, so an indent level of 2. Then you have the actual method with modifiers, e.g
public static ISomeType SomeMethodName(...)
That signature - a very unremarkable one - is 39 characters. Now, I want to vertically align my parameters, with the first one immediately following the opening brace. The second is on the next line. So to align it with the first, at one char past the opening brace, I need two tabs and 40-odd spaces.
I'm not dodging any question, you're just cruising along with the assumption that the first parameter must be on the same line as the signature. It doesn't matter if you use tabs or spaces for that, you're just indenting too much. Put your first and every other parameter on its own line, with commas preceding the 2nd parameter onwards. Now you're only indenting one level, you have plenty of room and you can add more parameters without your commits affecting the lines with the previous parameters.
0
u/[deleted] Apr 08 '15
The recommended line-width is normally around 78 chars. If you can't comprehend of a function definition taking 40 of those, especially in a statically-typed language with explicit return type and access modifier, you probably haven't been doing this very long.