From: Paul Koning <paulkoning@comcast.net>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org,
Jakub Jelinek <jakub@redhat.com>,
Tobias Burnus <tobias@codesourcery.com>,
Michael Meissner <meissner@linux.ibm.com>
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)
Date: Thu, 05 Dec 2019 16:24:00 -0000 [thread overview]
Message-ID: <4A56F4A2-4FAB-4FF3-AFEB-13142CEC9E4B@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1912051612270.14354@digraph.polyomino.org.uk>
> On Dec 5, 2019, at 11:17 AM, Joseph Myers <joseph@codesourcery.com> wrote:
>
> On Thu, 5 Dec 2019, Thomas Schwinge wrote:
>
>> In the relevant session at the GNU Tools Cauldron 2019, Michael Meissner
>> stated that even he is not using a 80 x 24 terminal anymore, and that
>> should tell us something. ;-)
>>
>> So, I formally propose that we lift this characters per line restriction
>> from IBM punch card (80) to mainframe line printer (132).
>
> I thought these line lengths were based on readability studies suggesting
> lengths that lines shorter than 80 columns were more readable?
That's certainly a general rule. There is a reason why books aren't wide, and why newspapers have columns. The eye can't deal well with long lines. So while 132 column lines are certainly possible with modern computers, it doesn't mean they are desirable.
paul
next prev parent reply other threads:[~2019-12-05 16:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8be82276-81b1-817c-fcd2-51f24f5fe2d2@codesourcery.com>
[not found] ` <20191205151515.GS10088@tucnak>
2019-12-05 15:47 ` Thomas Schwinge
2019-12-05 16:04 ` Jakub Jelinek
2019-12-05 20:21 ` Segher Boessenkool
2019-12-05 16:17 ` Joseph Myers
2019-12-05 16:24 ` Paul Koning [this message]
2019-12-05 16:40 ` Jeff Law
2019-12-05 16:55 ` [RFC] Characters per line: from punch card (80) to line printer (132) Florian Weimer
2019-12-05 17:55 ` Andrew Stubbs
2019-12-05 18:12 ` Eric Gallager
2019-12-05 18:22 ` Robin Curtis
2019-12-05 19:16 ` James Secan
2019-12-06 9:22 ` Andrew Stubbs
2019-12-05 16:44 ` [RFC] Characters per line: from punch card (80) to line printer (132) (was: [Patch][OpenMP/OpenACC/Fortran] Fix mapping of optional (present|absent) arguments) Michael Matz
2019-12-05 17:03 ` Jonathan Wakely
2019-12-05 18:07 ` Marek Polacek
2019-12-05 20:06 ` Segher Boessenkool
2019-12-05 20:38 ` Marek Polacek
2019-12-05 22:02 ` Segher Boessenkool
2019-12-05 20:56 ` Jonathan Wakely
2019-12-05 22:19 ` Segher Boessenkool
2019-12-05 22:34 ` Jonathan Wakely
2019-12-05 22:37 ` Jonathan Wakely
2019-12-05 23:02 ` Segher Boessenkool
2019-12-05 17:29 ` N.M. Maclaren
2019-12-05 20:12 ` Segher Boessenkool
2019-12-05 20:41 ` Jason Merrill
2019-12-05 18:54 ` [RFC] Characters per line: from punch card (80) to line printer (132) Martin Sebor
2019-12-05 20:32 ` Segher Boessenkool
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A56F4A2-4FAB-4FF3-AFEB-13142CEC9E4B@comcast.net \
--to=paulkoning@comcast.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=meissner@linux.ibm.com \
--cc=thomas@codesourcery.com \
--cc=tobias@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).