This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/33268] read ('(f3.3)'), a rejected due to the extra (...)
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Oct 2007 20:28:02 -0000
- Subject: [Bug fortran/33268] read ('(f3.3)'), a rejected due to the extra (...)
- References: <bug-33268-13404@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from burnus at gcc dot gnu dot org 2007-10-08 20:28 -------
> I am going to vote that this bug is invalid. IFORT and Sun F95 also reject
> this.
Remark: The compilers, which accept the ('(a)') all reject
READ(*,*), a
because of the comma after "*)" (g95, NAG f95); the compiler accepting this
extension (ifort, sunf95, gfortran) all do not accept the valid
READ ('(a)'), a
Thus viewed from the Fortran standard it is easy: If there is a comma after the
"(...)" it must be a format/default-character-expression, otherwise a
io-control-spec-list. Unfortunately, with gfortran we don't have this luxury as
we do support the vendor extension with the comma after the
"(io-control-spec-list)".
> Well from comment on comp.lang.fortran, I lost my argument. :)
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/05465f765b682279/
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33268