http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52325
Bug #: 52325 Summary: unclear error: Unclassifiable statement Classification: Unclassified Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassig...@gcc.gnu.org ReportedBy: kloe...@knmi.nl The given example code generates this error: unclassifiable.F90:9.4: cc%a = 1 1 Error: Unclassifiable statement at (1) while in fact it would be much more helpfull if the error would clearly state that the symbol is not yet defined (as the commented out lines do): unclassifiable.F90:16.5: d=1 1 Error: Symbol 'd' at (1) has no IMPLICIT type Especially in larger modules/programs having a clear error in case of this kind of variable naming msitakes/typos could save a lot of debugging time for gfortran users. Example code: module test_unclassifiable implicit none type test integer :: a end type test contains subroutine test_sub1(c) type(test), intent(out) :: c cc%a = 1 end subroutine test_sub1 ! subroutine test_sub2(c) ! integer :: c ! d=1 ! end subroutine test_sub2 end module test_unclassifiable