On Thu, Oct 01, 2015 at 11:19:37PM +0200, Dominique d'Humières wrote:
> Without initialization the errors are of the kind:
>
> Error: Expression at (1) must be of INTEGER type, found *
>
> see https://gcc.gnu.org/ml/gcc-bugs/2015-10/msg00081.html. Should not we get
> the same message with initia
Without initialization the errors are of the kind:
Error: Expression at (1) must be of INTEGER type, found *
see https://gcc.gnu.org/ml/gcc-bugs/2015-10/msg00081.html. Should not we get
the same message with initialization?
Cheers,
Dominique
> Well, ahem, gfortran does have several error messages that use the
> standard notation. I know. I wrote some of them. :-)
>
> I'll simply change it to "Expecting an INTEGER at %L”
Thanks. I have no objections to using the full standard terminology (scalar
integer expression), but not the sho
On Thu, Oct 01, 2015 at 09:19:15PM +0200, FX wrote:
> > 2015-10-01 Steven G. Kargl
> >
> > PR fortran/67802
> > * decl.c (add_init_expr_to_sym): Numeric constant for character
> > length must be an INTEGER.
> >
> > 2015-10-01 Steven G. Kargl
> >
> > PR fortran/67802
> >
> 2015-10-01 Steven G. Kargl
>
> PR fortran/67802
> * decl.c (add_init_expr_to_sym): Numeric constant for character
> length must be an INTEGER.
>
> 2015-10-01 Steven G. Kargl
>
> PR fortran/67802
> * gfortran.dg/pr67802.f90: New test.
OK, but not with that e
