[J3] Vector subscripts and INTENT(INOUT)

[John Reid]

Bill Long via J3 wrote:
> I’m still sympathetic to Rafik’s comment.  When a statement about vector-subscripted array sections has been in the standard since array sections were introduced, and then disappears in a draft of the next standard, it is at least concerning, and naturally interpreted as a technical change.
> 
> In fact, there is a minor technical change in this case, in that the old sentence did not account for the case of the dummy argument having the VALUE attribute.
> 
> That said, I think it would be helpful to include a sentence in 9.5.3.2.2 something like
> 
>   “Additional limitations related to the use of an array section with a vector subscript as an actual argument are in 15.5.2.4."

I think you mean 9.5.3.3.2.

John.


> 
> That is purely editorial (in bounds for the next J3 meeting) and would help avoiding future confusion.
> 
> Cheers,
> Bill
> 
> 
>> On May 15, 2018, at 11:46 AM, Rafik Zurob <rzurob at ca.ibm.com> wrote:
>>
>>>
>>> I did go back and look at old standards.  F2008, in the “Vector
>>> subscript” subclause of 6, has “An array section with a vector
>>> subscript shall not be argument associated with a dummy array that
>>> is defined or redefined.”.    That is the “shall not” rule that
>>> supports the factual claim in the argument association clause that
>>> the dummy is undefinable.   The same rule is in all the standards
>>> going back to F90.   For some reason it was dropped in the F2018
>>> draft, which is the one I was originally reading.  If it was added
>>> back into F2018, then there would be a rule-based justification for
>>> the claim that the dummy argument is not definable. I would find
>>> that a substantial improvement.
>>>
>>>
>>
> …
> 
>>
>> I fully support putting the rule back in F2018 draft. (Or if there is good reason for dropping it, I would appreciate learning it.)
>>
>> Regards
>>
>> Rafik
> 
> Bill Long                                                                       longb at cray.com
> Principal Engineer, Fortran Technical Support &   voice:  651-605-9024
> Bioinformatics Software Development                      fax:  651-605-9143
> Cray Inc./ 2131 Lindau Lane/  Suite 1000/  Bloomington, MN  55425
> 
>