From: Harald Anlauf <anlauf@gmx.de>
To: Tobias Burnus <tobias@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] Fortran: Accept -std=f2023, update line-length for Fortran 2023
Date: Fri, 17 Nov 2023 20:07:31 +0100 [thread overview]
Message-ID: <8473b1ba-b29f-47a2-bc49-427838db5625@gmx.de> (raw)
In-Reply-To: <6b62f178-e3c4-4bdb-b7cc-eb57477cd27d@codesourcery.com>
Hi Tobias,
On 11/17/23 12:38, Tobias Burnus wrote:
> Hi Harald, hi all,
>
> On 16.11.23 20:30, Harald Anlauf wrote:
>> According to the standard one can have 999999 lines with only
>> "&" and then an ";", but then only 100 lines with 10000 characters.
>
> I believe a single '&' is not valid, you either need '&&' or something
> else + '&'; thus, you can have only half a million lines + 1.
after looking at the F2023 standard again I wonder why
they did such a disservice to compiler developers...
You are right: a single '&' is not valid.
6.3.2.4 also has:
"When used for continuation, the “&” is not part of the statement"
And 6.3.2.5 (also 6.3.3.4): "The “;” is not part of the statement".
So a million "&"-continued lines is possible in free form.
For fixed form, 6.3.3.1 has: "If a source line contains only characters
of default kind, it shall contain exactly 72 characters; otherwise, its
maximum number of characters is processor dependent."
I wonder what I should make out of this...
> In the code, I still use 1,000,000 but now with a comment.
Yeah, for the time being this is the most reasonable solution.
Let's claim that the 10^6 line limit is the new GNU standard ;-)
Cheers,
Harald
next prev parent reply other threads:[~2023-11-17 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 13:01 [Patch] Fortran: Accept -std=f2023 support, " Tobias Burnus
2023-11-16 19:30 ` Harald Anlauf
2023-11-17 11:38 ` [Patch] Fortran: Accept -std=f2023, update line-length for Fortran 2023 (was: [Patch] Fortran: Accept -std=f2023 support, update line-length for Fortran 2023) Tobias Burnus
2023-11-17 12:06 ` [Patch] Fortran: Accept -std=f2023, update line-length for Fortran 2023 Mikael Morin
2023-11-17 19:07 ` Harald Anlauf [this message]
2024-01-02 19:31 ` Harald Anlauf
2024-01-02 19:37 ` Steve Kargl
2024-01-02 19:51 ` Harald Anlauf
2023-11-17 3:38 ` [Patch] Fortran: Accept -std=f2023 support, " Jerry D
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=8473b1ba-b29f-47a2-bc49-427838db5625@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.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).