From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
Rimvydas Jasinskas <rimvydasjas@gmail.com>,
Rimvydas Jasinskas via Fortran <fortran@gcc.gnu.org>
Subject: Re: Fortran: Use non conflicting file extensions for intermediates [PR81615]
Date: Tue, 2 Jan 2024 08:16:26 +0000 [thread overview]
Message-ID: <CAGkQGi+rmN8-pHUdYgtSDshiBH1PGRQmcdPWgODt7b3t2Np8mA@mail.gmail.com> (raw)
In-Reply-To: <f199f594-fc6f-48c4-b431-56418a7593e4@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]
Hi Harald,
'from' is slightly better but either will be understood.
Cheers
Paul
Happy New Year to you all!
On Mon, 1 Jan 2024 at 21:25, Harald Anlauf <anlauf@gmx.de> wrote:
> Hi Thomas!
>
> Am 30.12.23 um 12:08 schrieb Thomas Koenig:
> > Replying to myself...
> >
> >
> >> I think this also desevers a mention in changes.html. Here is something
> >> that I came up with. OK? Or does anybody have suggestions for a better
> >> wording?
> >>
> >
> > Or maybe this is better:
> >
> > diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> > index 4b83037a..d232f631 100644
> > --- a/htdocs/gcc-14/changes.html
> > +++ b/htdocs/gcc-14/changes.html
> > @@ -282,8 +282,14 @@ a work-in-progress.</p>
> >
> > <!-- <h3 id="d">D</h3> -->
> >
> > -<!-- <h3 id="fortran">Fortran</h3> -->
> > -
> > +<h3 id="fortran">Fortran</h3>
> > +<ul>
> > + <li> With the <code>-save-temps</code> option, preprocessed files
> > + with the <code>.fii</code> extension will be generated for
> > + free-form source files such as <code>.F90</code> and
> > + <code>.fi</code> for fixed-form files such as <code>.F</code>.
> > + </li>
> > +</ul>
> > <!-- <h3 id="go">Go</h3> -->
>
> I slightly prefer this variant.
>
> I wonder if it were better to write "generated from" instead of
> "generated for". A native speaker might help here.
>
> While at it: gfortran now accepts "-std=f2023", which implies that
> the limit for line-length in free-form has been increased to 10000
> characters, and statements may have up to 1 million characters.
> (See Tobias' commit r14-5553-gb9eba3baf54b4f).
>
> I'd consider this as important as the other change... ;-)
>
> Thanks,
> Harald
>
> > <!--
> > .................................................................. -->
> >
> >
> >
>
>
next prev parent reply other threads:[~2024-01-02 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 4:32 Rimvydas Jasinskas
2023-12-20 19:29 ` Harald Anlauf
2023-12-24 1:33 ` Rimvydas Jasinskas
2023-12-27 20:34 ` Harald Anlauf
2023-12-28 7:09 ` Rimvydas Jasinskas
2023-12-28 20:31 ` Harald Anlauf
2023-12-30 11:01 ` Thomas Koenig
2023-12-30 11:08 ` Thomas Koenig
2024-01-01 21:25 ` Harald Anlauf
2024-01-02 8:16 ` Paul Richard Thomas [this message]
2024-01-02 9:01 ` Thomas Koenig
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=CAGkQGi+rmN8-pHUdYgtSDshiBH1PGRQmcdPWgODt7b3t2Np8mA@mail.gmail.com \
--to=paul.richard.thomas@gmail.com \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=rimvydasjas@gmail.com \
--cc=tkoenig@netcologne.de \
/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).