The tyranny of the Hollerith punched card

Re:The tyranny of the Hollerith punched card by DanBC on Monday June 06, 2016 @10:18AM (#11846926)

> It's very annoying when I read code that doesn't use the 80-character limit, because my terminal is not guaranteed to be as wide as theirs, and I really don't like resizing my terminal window to fit their line length.

Considering the numbers of programmers in the world, and how long they've been working with text, and how much annoyance text breaks / line wrapping / format flowing causes it's kind of surprising that there isn't better ways of wrapping lines without line breaks.

What's current best practice? Or is it just down to the project style guide?

[ Parent | on HN ]

Re:The tyranny of the Hollerith punched card by andrey_utkin on Monday June 06, 2016 @11:10AM (#11847324)

I guess these are enough general: put operator sign before line break; don't break inside of the most nested expression; don't break between variable type and name...

There are more such rules which differ between standards (like Linux kernel style vs. PHP PSR-2 style), e.g. how to pad trailing lines of function call. Linux style says to align trailing lines at offset next to the opening brace. (This doesn't look good in case of long function name, though, but most of time readability of this way is very good.) K&R is referenced as an original of such style, just as everywhere in Linux coding style. Also Linux coding style is not just what is told in Documentation/CodingStyle - there are some unwritten tools which you'll encounter when you run scripts/checkpatch.pl or get reviews on your patch submission.

[ Parent | on HN ]

Re:The tyranny of the Hollerith punched card by zyxley on Monday June 06, 2016 @11:58AM (#11847713)

gofmt comes to mind here. It renders the particulars of what you do while writing a non-issue by taking any valid Go input and producing a "canonical" final formatted version.

[ Parent | on HN ]