This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/18985] opening unit 6 messes up print
- From: "Thomas dot Koenig at online dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Dec 2004 08:45:57 -0000
- Subject: [Bug libfortran/18985] opening unit 6 messes up print
- References: <20041214133957.18985.Thomas.Koenig@online.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From Thomas dot Koenig at online dot de 2004-12-15 08:45 -------
(In reply to comment #1)
> I think that's what intended
That's what's for discussion :-)
> g77 behaves the same way.
I think this is a bug, too.
My thinking is that writing to * (or PRINTing)
should go to standard output, and that unit 6
just happens to be a convention for a preconnected
unit that does the same thing.
ifort, for example, does things differently:
$ cat open2.f
open(6,file="foo.dat")
print *,"hello, world"
end
$ ifort open2.f
$ ./a.out
hello, world
$ ifort -V
Intel(R) Fortran Itanium(R) Compiler for Itanium(R)-based applications
Version 8.1 Build 20041123 Package ID: l_fc_pc_8.1.023
Copyright (C) 1985-2004 Intel Corporation. All rights reserved.
ifort: Command line error: no files specified; for help type "ifort -help"
Does the Fortran standard say anything that messing with unit 6
can be bad news for unit * ?
I have marked the bug as "enhancement" with this.
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18985