3 ms·
Remember that long lines aren't just a problem for display. Longer lines might indicate that the code is either nested too deep, likely too complicated. Or poo
by cerved 5y ago
Remember that long lines aren't just a problem for display.
Longer lines might indicate that the code is either nested too deep, likely too complicated. Or poorly named withUnreadableRidicouslyLongWeirdWhatsGoingOnHereName.
It's also problematic if the line ends up doing too much, ie. lots of chained method, since VCS track changes per line.
While editors do a good job at word wrapping, they're not always excellent. Humans may do a better job.
Note that the kennels style guide isn't fixed at 80 characters but strongly preferred.
"Coding style is all about readability and maintainability using commonly available tools.
The limit on the length of lines is 80 columns and this is a strongly preferred limit.
Statements longer than 80 columns will be broken into sensible chunks, unless exceeding 80 columns significantly increases readability and does not hide information. Descendants are always substantially shorter than the parent and are placed substantially to the right. The same applies to function headers with a long argument list. However, never break user-visible strings such as printk messages, because that breaks the ability to grep for them."