From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: woodzltc@cn.ibm.com
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA] New testcase to evaluate Fortran substring expression
Date: Mon, 01 Aug 2005 06:23:00 -0000 [thread overview]
Message-ID: <200508010622.j716MDiG002521@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.63.0507291616040.17779@localhost.localdomain> (message from Wu Zhou on Fri, 29 Jul 2005 16:21:37 +0800 (CST))
Date: Fri, 29 Jul 2005 16:21:37 +0800 (CST)
From: Wu Zhou <woodzltc@cn.ibm.com>
Sorry, I am not very sure what is the maximum limit of a line in the sources
and comments. Maybe it is 72? or 80, or any other number? Maybe I can
choose to use the smaller one?
We're not too strict about it. The default value for "fill-column" in
emacs is 70, so I'd say it's more 72 than 80, especially for comments.
But for code it's ok to have slightly longer lines, if it improves the
readability of your code, as long as things stay under 80. Please
don't put anything in column 80 (or 79 if you live in a non-Fortran
world ;-), because some terminals wrap as soon as you put something in
the last column.
By the way, there is a good reason for following this practice, even
if many people are using environments that can display more than 80
characters on a line. There has been quite a bit of research on
optimal line length by psychologists. Making lines to long makes
things difficult to read; people start skipping lines. Look at some
well typeset books and count the number of characters on it. You'll
end up with somthing 70-ish for most of them
Mark
next prev parent reply other threads:[~2005-08-01 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 4:02 Wu Zhou
2005-07-03 18:57 ` Daniel Jacobowitz
2005-07-09 3:12 ` Wu Zhou
2005-07-14 23:46 ` Daniel Jacobowitz
2005-07-15 5:25 ` Wu Zhou
2005-07-15 11:49 ` Wu Zhou
2005-08-01 2:12 ` Daniel Jacobowitz
2005-08-01 4:44 ` Wu Zhou
2005-08-01 6:23 ` Mark Kettenis [this message]
2005-08-02 3:10 ` Daniel Jacobowitz
2005-08-02 10:16 ` Wu Zhou
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=200508010622.j716MDiG002521@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=woodzltc@cn.ibm.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