[Bug fortran/50252] [OOP] Error message on call x%y (x not declared) can be more informative

2014-01-07 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50252 Dominique d'Humieres dominiq at lps dot ens.fr changed: What|Removed |Added Status|UNCONFIRMED |NEW

[Bug fortran/50252] [OOP] Error message on call x%y (x not declared) can be more informative

2011-09-01 Thread arjen.markus895 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50252 --- Comment #3 from Arjen Markus arjen.markus895 at gmail dot com 2011-09-01 07:18:30 UTC --- Hi Janus, that seems quite to the point and it is much more straightforward than my (minimal) adjustment. Thanks. The reason I brought this is that is

[Bug fortran/50252] [OOP] Error message on call x%y (x not declared) can be more informative

2011-09-01 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50252 --- Comment #4 from janus at gcc dot gnu.org 2011-09-01 11:28:35 UTC --- Unfortunately the patch in comment #2 did not survive the regression test. It fails at least on: FAIL: gfortran.dg/dynamic_dispatch_10.f03 -O0 (test for excess errors)

[Bug fortran/50252] [OOP] Error message on call x%y (x not declared) can be more informative

2011-08-31 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50252 janus at gcc dot gnu.org changed: What|Removed |Added CC||janus at gcc dot gnu.org

[Bug fortran/50252] [OOP] Error message on call x%y (x not declared) can be more informative

2011-08-31 Thread janus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50252 --- Comment #2 from janus at gcc dot gnu.org 2011-08-31 19:31:10 UTC --- Ok, here is one thing that could be easily done. Preliminary patch, not regtested. Does this sound like an improvement? Index: gcc/fortran/match.c