https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109662
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to anlauf from comment #1)
> I also interpret F2018:13.11.3.1 that a value-separator may follow only
> a name-value subsequence but not immediately the namelist-group-name.
> This is also what other brands (NAG, Intel, Nvidia) accept.
>
> Thus confirmed.
Yes, definitely a bug. The issue isn't the value-separator. It's
item (3) from 13.11.3.1.
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,
There needs to be a blank following '&stuff'. Now, the question
becomes "what happens with this line?"
character(17) :: list = '&stuff , n = 666/'
The next requirement comes into play
(4) a sequence of zero or more name-value subsequences
separated by value separators, and
Probably should tag Jerry.
