(j3.2006) Is <initial-data-target> required to have the SAVE attribute?

[Malcolm Cohen]

The claim that there are no constraints on <initial-data-target> that
mention the SAVE attribute is incorrect.  There is only one constraint on
<initial-data-target>, C766, and indeed it does mention SAVE.

Cheers,
-- 
..............Malcolm Cohen, NAG Oxford/Tokyo.

-----Original Message-----
From: j3-bounces at mailman.j3-fortran.org
[mailto:j3-bounces at mailman.j3-fortran.org] On Behalf Of Van Snyder
Sent: Wednesday, May 17, 2017 8:41 AM
To: j3 <j3 at j3-fortran.org>
Subject: (j3.2006) Is <initial-data-target> required to have the SAVE
attribute?

Is <initial-data-target> required to have the SAVE attribute?

I can't find such a requirement.  If it existed, I would have expected it to
be in 7.5.4.6 "Default initialization for components" where
"data-pointer-initialization compatible" is defined.  That term is
referenced in constraints C765 and C811.  There are no constraints on
<initial-data-target> that mention the SAVE attribute.

I can imagine allowing the <initial-data-target> in R743 not to have the
SAVE attribute, but I cannot imagine allowing that in R805.  Allowing it in
R743 would be inconsistent with nonpointer initialization, which requires a
<constant-expr>.


_______________________________________________
J3 mailing list
J3 at mailman.j3-fortran.org
http://mailman.j3-fortran.org/mailman/listinfo/j3

________________________________________________________________________
This e-mail has been scanned for all viruses by Star.
________________________________________________________________________