1c91d9bdea
Before emitting a warning message, code should check that the usage in question should be diagnosed by calling ShouldWarn(). A fair number of sites in the code do not, and can emit portability warnings unconditionally, which can confuse a user that hasn't asked for them (-pedantic) and isn't terribly concerned about portability *to* other compilers. Add calls to ShouldWarn() or IsEnabled() around messages that need them, and add -pedantic to tests that now require it to test their portability messages, and add more expected message lines to those tests when -pedantic causes other diagnostics to fire.
35 lines
1.2 KiB
Fortran
35 lines
1.2 KiB
Fortran
! RUN: %python %S/test_errors.py %s %flang_fc1 -pedantic
|
|
! Confirm enforcement of constraint C723 in F2018 for procedure pointers
|
|
|
|
module m
|
|
contains
|
|
subroutine subr(parg)
|
|
!PORTABILITY: A dummy procedure pointer should not have assumed-length CHARACTER(*) result type
|
|
procedure(character(*)), pointer :: parg
|
|
!ERROR: An assumed (*) type parameter may be used only for a (non-statement function) dummy argument, associate name, character named constant, or external function result
|
|
procedure(character(*)), pointer :: plocal
|
|
print *, parg()
|
|
plocal => parg
|
|
call subr_1(plocal)
|
|
end subroutine
|
|
|
|
subroutine subr_1(parg_1)
|
|
!PORTABILITY: A dummy procedure pointer should not have assumed-length CHARACTER(*) result type
|
|
procedure(character(*)), pointer :: parg_1
|
|
print *, parg_1()
|
|
end subroutine
|
|
end module
|
|
|
|
character(*) function f()
|
|
f = 'abcdefgh'
|
|
end function
|
|
|
|
program test
|
|
use m
|
|
character(4), external :: f
|
|
procedure(character(4)), pointer :: p
|
|
p => f
|
|
call subr(p)
|
|
end
|
|
|