This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist



------- Comment #7 from steven dot chapel at sbcglobal dot net  2007-07-17 12:49 -------
(In reply to comment #5)
> if all its trying to do is WRITE to the console
> use WRITE(unit=6) and don't give it a filename at all.
> 
> Will this work for you?

Not really. It's been written that way so that you can easily change where the
output goes by changing one line of code. Hardcoding the output to go to the
console defeats the purpose. I'm also not the author of the code, and I don't
want to have to manually change every line of code like that in my local copy
with each release of NONMEM.

> I think it should be CONOUT$ (ie you had it right the first time).
> The following works with g77 (and the old Intel Fortran ivf compiler)

That's what it was the first time, when I got Fortran runtime error: Bad file
descriptor. That's why I changed it to con. If there's something else I can
change it to, I can fairly easily manually make that change with each release
of NONMEM because it's only one line of code.


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]