[Bug libfortran/18985] opening unit 6 messes up print

2008-08-07 Thread schilds at sun dot ac dot za


--- Comment #6 from schilds at sun dot ac dot za  2008-08-07 19:07 ---
This is a serious bug, make no mistake. It causes existing Fortran 77 code to
fail. It's wasted a lot of my time and, no doubt, a lot of other, good peoples'
too. 

The print*, (or write(*,*)) statement certainly _IS_ standard Fortran 77 and
its ubiquitousness should make fixing this bug a priority.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18985



[Bug libfortran/18985] opening unit 6 messes up print

2008-08-08 Thread schilds at sun dot ac dot za


--- Comment #8 from schilds at sun dot ac dot za  2008-08-08 08:31 ---
What does Fortran 2003 have to do with legacy mode? Nothing. So far as I know
the GCC compiler is at odds with Solaris, Intel, Vax, you name it. All of these
allowed you to touch unit 6 without affecting the print*, (or write(*,*))
statement. The behaviour is therefore both unexpected and difficult to track
down (not even a warning). 

This is a serious bug, make no mistake. It causes existing Fortran 77 code to
fail. It's wasted a lot of my time and, no doubt, a lot of other, good peoples'
too. The ubiquitousness of the print*, (or write(*,*)) statement makes fixing
this bug a priority.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18985



[Bug libfortran/18985] opening unit 6 messes up print

2008-08-09 Thread schilds at sun dot ac dot za


--- Comment #11 from schilds at sun dot ac dot za  2008-08-09 07:27 ---
Jeez! After reading what all of you have said ... I see this code does actually
do something as crazy (and simple) as set the logical unit number for a file to
6, in a subroutine (when I had thought they had only done writes). 

Yes, this is a known Fortran issue from way back. I apologise profusely for
wasting your time in the manner I have. Again, I apologise.

P.S. If it makes you feel better, just think of the task I have ahead of me.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18985