This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [PATCH, fortran testsuite] read_eof.f90 open file bug
On Thu, Dec 30, 2004 at 10:12:35PM +0000, Paul Brook wrote:
> One solution might be to treat std{in,out,err} as files in their own right,
> rather than looking to see what they're actually connected to. It's then up
> to the user to make sure they don't overlap.
I think this is a good idea. Poking around file descriptors to
see what they are connected to just doesn't agree with UNIX
philosophy.
I would also suggest that all UNIX special files, not just
/dev/null, shouldn't be checked. I think they are outside the scope
of the Fortran standard, because they violate Fortran semantics
(like being able to read back what you wrote for /dev/null :-)
Thomas