From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Per Bothner <per@bothner.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, gcc@gcc.gnu.org
Subject: Re: Trigraph warnings when compiling linux-2.4.0-prerelease1
Date: Tue, 02 Jan 2001 14:50:00 -0000 [thread overview]
Message-ID: <3A525A8D.2CBF355@moene.indiv.nluug.nl> (raw)
In-Reply-To: <m2k88d7mwe.fsf@kelso.bothner.com>
Per Bothner wrote:
> Linus Torvalds <torvalds@transmeta.com> writes:
> > -Wtrigraphs
> > Warn if any trigraphs are encountered (assuming they are enabled).
> I read "assuming they are enabled" is a very poor way of saying "warn about
> constructs that would be read as trigraphs if trigraphs were enabled."
Note how much of the actual meaning of the sentence is elided by the
formulation in the documentation - these sort of sentences are hard to
read and easy to misunderstand for non-native speakers, e.g. "are
encountered" vs. "would be read as". In fact, I read it exactly the
same way Linus did (once I managed to wrap my head around the notion of
"trigraphs" :-( )
[ Use Fortran 77 - only 48 legal characters :-)]
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)
next prev parent reply other threads:[~2001-01-02 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200101020654.WAA03344@neosilicon.transmeta.com>
2001-01-01 23:00 ` Linus Torvalds
2001-01-02 0:23 ` Fergus Henderson
2001-01-02 9:18 ` Joe Buck
2001-01-02 10:38 ` Linus Torvalds
2001-01-02 10:58 ` Joe Buck
2001-01-02 11:15 ` Linus Torvalds
2001-01-02 11:50 ` Per Bothner
2001-01-02 11:55 ` Linus Torvalds
2001-01-02 12:40 ` Joe Buck
2001-01-02 13:50 ` Linus Torvalds
2001-01-02 14:50 ` Toon Moene [this message]
2001-01-03 23:39 ` Zack Weinberg
2001-01-02 13:27 dewar
2001-01-02 15:20 ` Joe Buck
2001-01-02 19:03 ` Fergus Henderson
2001-01-03 11:21 ` Joe Buck
-- strict thread matches above, loose matches on Subject: below --
2001-01-02 12:05 dewar
2001-01-02 9:26 dewar
2001-01-01 9:56 Rich Baum
2001-01-01 11:50 ` Tim Hollebeek
2001-01-01 15:16 ` Joe Buck
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=3A525A8D.2CBF355@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=gcc@gcc.gnu.org \
--cc=per@bothner.com \
--cc=torvalds@transmeta.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).