Aleksandar Donev writes:
> Here is the piece of the standard again:
>
> Action that affects the value of the argument or any part of it must
> be taken through the dummy argument unless
> a. the dummy argument has the {pointer} attribute,
> b. the part is all or part of a pointer subobject, or
> c. the dummy argument has the {target} attribute, the dummy
> argument does not have intent {in}, the dummy argument is scalar
> or an assumed-shape array, and the actual argument is a target
> other than an array section with a vector subscript.
>
> > Um.... And that's why the last word of the part you snipped was "or"?
>
> Well, I am reading the "OR" as being between a, b and c, i.e. either POINTER or
> TARGET imply possible aliasing. Then part c has a ", and the actual...", so part
> c I am reading as all being connected with AND.
Oh. Ok. Yes, I agree with that. (On the larger question, I'll
remain silent. Interp 125 always did give me a headache; I don't
think I'm up to re-delving into it).
--
Richard Maine | Good judgment comes from experience;
[log in to unmask] | experience comes from bad judgment.
| -- Mark Twain
|