3 ms·
> The patch rejected by Linus is a good example why you want "long" lines: the argument list of a function was broken into two lines, with the second line only
by janaagaard 5y ago
> The patch rejected by Linus is a good example why you want "long" lines: the argument list of a function was broken into two lines, with the second line only containing a single function argument.
I would chop the arguments, putting a single one on each line.
- _ph_ 5y agoThat would be a good alternative, especially if you use the space for documentation. I don't think there is one right way to do it, but certainly just wrapping arguments as if they were flowing text was the worst :)
- necovek 5y agoFlowing text is almost never wrapped that way: I make a reference to handling of "widow" words above, and they're very undesired in typeset text. Getting to know those simple gotchas about where to avoid line breaking can help with both prose and code writing.