This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Characters per line: from punch card (80) to line printer (132) (was: [Patch][OpenMP/OpenACC/Fortran] Fix mapping of optional (present|absent) arguments)
- From: Michael Matz <matz at suse dot de>
- To: Thomas Schwinge <thomas at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Thu, 5 Dec 2019 16:44:21 +0000 (UTC)
- Subject: Re: [RFC] Characters per line: from punch card (80) to line printer (132) (was: [Patch][OpenMP/OpenACC/Fortran] Fix mapping of optional (present|absent) arguments)
- References: <8be82276-81b1-817c-fcd2-51f24f5fe2d2@codesourcery.com> <20191205151515.GS10088@tucnak> <87lfrq6ahm.fsf@euler.schwinge.homeip.net>
Hello,
(oh a flame bait :) )
On Thu, 5 Dec 2019, Thomas Schwinge wrote:
> So, I formally propose that we lift this characters per line restriction
> from IBM punch card (80) to mainframe line printer (132).
>
> Tasks:
>
> - Discussion.
I object to cluttering code in excuse for using sensible function names or
temporaries that otherwise can help clearing up code. Using 132-char
lines is cluttering code:
- long lines are harder to read/grasp: vertical eye movement is easier
than horizontal, and source code should be optimized for
reading, not writing
- long lines make it impossible to have two files next to each other at a
comfortable font size
- long lines are incompatible with existing netiquette re emails, for
instance
So, at least for me, that my terminals are 80 wide (but not x24) has
multiple reasons, and the _least_ of it is because that's what punch cards
had.
Ciao,
Michael.