This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/43851] Add _gfortran_error_stop_numeric
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Jul 2010 13:47:50 -0000
- Subject: [Bug fortran/43851] Add _gfortran_error_stop_numeric
- References: <bug-43851-13404@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #10 from burnus at gcc dot gnu dot org 2010-07-19 13:47 -------
(In reply to comment #9)
> There is one last improvement we can do here. Currently we are using
> gfc_match_init_expr. This works fine, but the error messages are worded toward
> initialization expressions and not stop codes. We could generalize the
> messages in gfc_match_init_expr or come up with a way to either signal a
> different message for a stop code or create a new function such as
> gfc_match_stopcode_expr.
Is this needed? The standard essentially says that is an initialization
expression is required for STOP.
(To be more precises: Fortran 2003's term "initialization expression" has been
changed to "constant expression" in F2008 and STOP takes constant expressions
as argument.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43851