public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: Re: Fortran: Use non conflicting file extensions for intermediates [PR81615]
Date: Mon, 1 Jan 2024 22:25:03 +0100	[thread overview]
Message-ID: <f199f594-fc6f-48c4-b431-56418a7593e4@gmx.de> (raw)
Message-ID: <20240101212503.17tHcM3URpKiatKp1IU7E-k0hUbz87r25P18_b-vu0I@z> (raw)
In-Reply-To: <f7db55b8-9150-4e54-b172-69e98ae57e03@netcologne.de>

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

>   <!-- 
> .................................................................. -->
> 
> 
> 



  reply	other threads:[~2024-01-01 21:25 UTC|newest]

Thread overview: 13+ 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-20 19:29   ` Harald Anlauf
2023-12-24  1:33   ` Rimvydas Jasinskas
2023-12-27 20:34     ` Harald Anlauf
2023-12-27 20:34       ` Harald Anlauf
2023-12-28  7:09       ` Rimvydas Jasinskas
2023-12-28 20:31         ` Harald Anlauf
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 [this message]
2024-01-01 21:25           ` Harald Anlauf

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=f199f594-fc6f-48c4-b431-56418a7593e4@gmx.de \
    --to=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    /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).