(j3.2006) does move_alloc violate restrictions in 12.5.2.13?

[Van Snyder]

On Wed, 2009-10-28 at 12:02 -0700, Jim Xia wrote:
> 
> 
> > Kurt answered this question yesterday.  MOVE_ALLOC (at least as
> > described in the standard, independently of how IBM implements it)
> > performs all of its actions by way of its dummy arguments, not by
> host
> > association, not by use association, not by storage association, not
> by
> > construct association.
> 
> 
> This IS about argument association.  If it helps, consider the
> analogies between the two calls 
> 
> 
> CALL FOO (A, A) 
> 
> vs. 
> 
> CALL MOVE_ALLOC (FROM, TO) 
> 
> 
> The fact is there is only ONE actual argument survives the call.  BUT,
> during the execution of MOVE_ALLOC, it has to be associated with both
> FROM and TO. 

This is a problem for the calling scoping unit, not for the intrinsic
subroutine.  The same problem exists for references to any procedure
that has more than one argument that is not INTENT(IN), regardless of
whether the procedure is intrinsic or not.

> 
> Cheers, 
> 
> 
> Jim Xia
> 
> XL Fortran Compiler Test
> IBM Toronto Lab at 8200 Warden Ave, Markham, On, L6G 1C7
> Phone (905) 413-3444  Tie-line 313-3444
> email: jimxia at ca.ibm.com
> D2/YF7/8200 /MKM
> 
> http://www.ibm.com/software/awdtools/fortran/xlfortran