Hi Harald,
Feedback, such as comments for improvement, are welcome.
It feels a bit strange to have a check for an allocatable
behind -fcheck=pointer, but I'm not sure that introducing
a special check option would really be worth it.
Regarding pointers: They are usually not nullified (unless
they are global). What do people think about adding a
NULL initializer to their data components when -fcheck=pointer is in
force?
On the other hand, for code like
module p
contains
subroutine foo
real, pointer, dimension(:) :: pp
print *,pp
end subroutine foo
end module p
we at least get a warning already.
Regarding size(x%re): You would have to chase the refs to find
the allocatable components.
However, I think your patch already makes the situation better for
the user, so I'd say it is good for trunk already; later improvements
are always possible.
Best regards
Thomas
