From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Tobias Burnus <burnus@net-b.de>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, wwwdocs] onlinedocs: Update link names for "GNU Fortran"
Date: Wed, 25 Jul 2007 13:26:00 -0000 [thread overview]
Message-ID: <46A74BFB.8080500@moene.indiv.nluug.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0707242236110.1770@acrux.dbai.tuwien.ac.at>
Gerald Pfeifer wrote:
> Hi Toon,
>
> On Tue, 24 Jul 2007, Toon Moene wrote:
>>> the Fortran compiler is now called "GNU Fortran Compiler" it used to be
>>> called "GNU Fortran 95 Compiler", but the "95" has been dropped since
>>> 4.2.0.
>> I would argue the other way around. Although GFortran *currently* is
>> mostly a Fortran 95 compiler, that isn't it's ultimate frontier. To me
>> that frontier is to track recent Fortran Standardisation efforts (if at
>> all possible) and hence refrain from putting a year designation into the
>> name of our efforts.
>
> is it possible there is no actual disagreement? ;-)
>
> My reading of Tobias' explanation and the patch itself is that he
> only added "95" for those older branches where the documentation
> itself actually uses that to bring the link in line with the actual
> documentation it points towards, and that he did not use "95" for
> the current development stream which does not use that any longer.
Ugh, sorry - I should have refrained from commenting, as Tobias'
original mail didn't arrive at my system (probably timed out while I was
at Ottawa).
--
Toon Moene - e-mail: toon@moene.indiv.nluug.nl - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.indiv.nluug.nl/~toon/
Who's working on GNU Fortran:
http://gcc.gnu.org/ml/gcc/2007-01/msg00059.html
prev parent reply other threads:[~2007-07-25 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 17:00 Tobias Burnus
2007-07-24 18:02 ` Gerald Pfeifer
2007-07-24 20:24 ` Toon Moene
2007-07-24 21:13 ` Gerald Pfeifer
2007-07-25 13:26 ` Toon Moene [this message]
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=46A74BFB.8080500@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=burnus@net-b.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).