[Bug fortran/20006] $ format extension doesn't work

[tow21 at cam dot ac dot uk]

------- Additional Comments From tow21 at cam dot ac dot uk  2005-04-12 14:46 -------
(In reply to comment #6) 
> Fatal I/O error for an extension that everybody agrees on? Wahoo! I'm not > 
> sure any compiler does that... 
 
But "everyone" doesn't agree on it. Otherwise it would be standard, not an 
extension,. If I compile with -pedantic -std=f95, then I'm saying I don't want 
any extensions, regardless of how many people agree on them. 
 
> In my mind, being pedantic (that is, issuing fatal errors) makes sense at 
> compile-time, but it is very harsh to do so at runtime. I can imagine how,  
> as a researcher, I would compile with -pedantic, be glad that no error turn 
> out, then run a one-week simulation code and see it issue a fatal error  
> instead of printing the results at the end... 
 
Then I think you're putting too much trust in -pedantic. This is why, for 
example, even if my codes compile with -pedantic, I'll run them thoroughly 
with -C. You can't catch every possible error at compile time. 
 
I would be equally annoyed if having run everything through with full 
-pedantic and error-checking on gfortran, I assumed that my code was fully 
standard-conforming, moved my code across to NAG fortran, and it crashed with 
 
Invalid edit descriptor beginning with '$' 
Program terminated by fatal I/O error 
zsh: 27142 abort (core dumped)  ./a.out 
 
which it would, because that's what it does now.  
 
Not, of course, that we can catch every standard violation, but I would expect 
that this be caught. 
 
 
 

-- 


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