Re: [patch, fortran] PR109662 Namelist input with comma after name accepted

[Harald Anlauf <anlauf@gmx.de>]

Steve,

On 5/8/23 02:13, Steve Kargl via Gcc-patches wrote:
> Harald,
> Thanks for keeping us honest.  I didn't check what other
> separators might cause a problem.
>
> After 2 decades of working on gfortran, I've come to conclusion
> that -std=f2018 should be the default.  When f2023 is ratified,
> the default becomes -std=f2023.  All GNU fortran extension
> should be behind an option, and we should be aggressive
> eliminating extensions.
>
> Yes, this means that 'real*4' and similar would require
> a -fallow-nonstandard-declaration option.
>

please don't let us get off-topic.

The issue behind the PR was F2018: 13.11.3.1, Namelist input,
which has

Input for a namelist input statement consists of
(1) optional blanks and namelist comments,
(2) the character & followed immediately by the namelist-group-name as
specified in the NAMELIST statement,
(3) one or more blanks,

where "blanks" was to be interpreted.  Separators are discussed
separately.

Jerry has resolved "," and ";".  Good.

There is another weird issue that is visible in the testcase
output in my previous mail for "!".  Reducing that further now
suggests that the EOF condition of the namelist read of the
single line affects the namelist read of the next multi-line read.

So this one is actually a different bug, likely libgfortran's
internal state.