This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/65684] Wrong error message when writing to a string
- From: "dominiq at lps dot ens.fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 08 Apr 2015 09:02:46 +0000
- Subject: [Bug fortran/65684] Wrong error message when writing to a string
- Auto-submitted: auto-generated
- References: <bug-65684-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65684
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-04-08
Ever confirmed|0 |1
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Honestly, do you really find that
> forrtl: severe (66): output statement overflows record, unit -5,
> file Internal List-Directed Write
is more helpful than
> At line 5 of file test.F90
> Fortran runtime error: End of record
?
Personally I don't. fortran directs the user to the line and file leading to
the run time error, then if the user does not understand what's wrong with
'write(str,*) 100', (s)he must really learn elementary Fortran.
> I agree we have no concern over compliance of gfortran here and the error
> message is accurate. So this is not a bug, but a request to enhance the error
> message in the case of the writing to a string. So, under the principle of
> being helpful to users, I will be willing to do this. It will have to wait
> until after the next release happens.
Several months ago I have browsed the bug list for fortran, libfortran (817
entries today) and I have seen about three dozens entries containing "message"
in their summary. I think a fraction of them are more urgent/easy to fix than
this one.
Now, if you really think this PR is important, nothing prevents you to submit a
patch!