[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-bugs
Subject:    [Bug fortran/45463] gfortran internal write bug
From:       "kargl at gcc dot gnu dot org" <gcc-bugzilla () gcc ! gnu ! org>
Date:       2010-08-31 16:49:01
Message-ID: 20100831164901.30002.qmail () sourceware ! org
[Download RAW message or body]



------- 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

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic