This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/45463] gfortran internal write bug
- From: "kargl at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Aug 2010 16:49:01 -0000
- Subject: [Bug fortran/45463] gfortran internal write bug
- References: <bug-45463-17588@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from kargl at gcc dot gnu dot org 2010-08-31 16:49 -------
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Sorry. When I looked after I had posted the question there was only one
> > > response and that response said it was a bug so I submitted this bug report.
> > > Now other people have posted saying that the program is non-conforming.
> >
> > Update: More responses in comp.lang.fortran bring up the point that if
> > trim(line)
> > is supposed to return a temporary, the code might be conforming. Seems that the
> > situation is not clear...
>
> IMNSHO, it's not conforming. trim(line) is associated with line.
> I don't see how one could interpret the standard in in other way.
>
> >
In fact, 16.5.7 in F2003, is fairly unambiguous. The code is
nonconforming.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45463