http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52539
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-03-10
14:52:51 UTC ---
(In reply to comment #1)
> I remember this being discussed before. Lets check the standard regarding
> encoding for namelists.
Well, the issue already occurs for list-directed reading ("read(99, *) str2").
One finds in F2008, 10.10.3p7 for list-directed read and in F2008, 10.11.3.3p7
for namelist read:
"When the next effective item is of type character, the input form consists of
a possibly delimited sequence of zero or more rep-chars whose kind type
parameter is implied by the kind of the effective item."
That clearly implies that it supports kind=4 (UCS-4, ISO 10646) characters -
and there is also no wording that the file encoding (UTF-8) doesn't apply to
list-directed read and to namelist read/write.
