I think I have found the answer:
12.4.1.6 Restrictions on dummy arguments not present
...
(7) If it is a pointer, it shall not be allocated, deallocated, nullified,
pointer-assigned, or supplied
as an actual argument corresponding to an optional nonpointer dummy argument.
^^^^^^^^^^
so
call sub2(a) ! <<< VALID or NOT?
is invalid for
subroutine sub2(b)
integer, optional :: b
end subroutine
but valid for
subroutine sub2(b)
integer, pointer, optional :: b
end subroutine
which is working with/without the patch.
Altough the burden is once again on the user, this could be detected
for contained procs and with -fwhole-file (is it worth opening a PR
for that?).
Dominique
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Fink-beginners mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.beginners
