--- Comment #3 from kargl at gcc dot gnu dot org 2008-12-08 19:31 ---
(In reply to comment #2)
> (In reply to comment #1)
> > - gfc_error (msg, sym->name, where, gfc_basic_typename
> > (sym->ts.type));
> > + gfc_fatal_error (msg, sym->name, where,
> > +
--- Comment #2 from jv244 at cam dot ac dot uk 2008-12-08 18:39 ---
(In reply to comment #1)
> - gfc_error (msg, sym->name, where, gfc_basic_typename
> (sym->ts.type));
> + gfc_fatal_error (msg, sym->name, where,
> + gfc_basic_typename (sym->ts.t
--- Comment #1 from kargl at gcc dot gnu dot org 2008-12-08 18:24 ---
Yeah, this has always bothered me. I typically use -fmax-errors=1 when
developing new code because of the run-on errors for simple mistakes.
This fixes the excessive errors in this case.
Index: symbol.c
=
