[J3] 18-265 and the PROTECTED attribute

[Van Snyder]

On Wed, 2018-11-14 at 18:32 -0800, Van Snyder via J3 wrote:
> In 18-265, Bill proposed a PROTECTED attribute for components.
> 
> 14-165r1 proposed a PROTECTED attribute for types.  14-165r1 proposed
> that the PROTECTED attribute could be specified for a type only in the
> scoping unit of a module.  It would be useful to be able to specify it
> for a type accessed by host association.
> 
> A colleague recently requested a PROTECTED annotation for USE to
> prohibit changing variables accessed by use association.  He also
> proposed a PROTECTED attribute for variables accessed by host
> association.  It would endure for the scope in which it is declared.
> Like ASYNCHRONOUS and VOLATILE, it doesn't create a new variable if it's
> specified for a variable accessed by host association.
> 
> PROTECTED, in all the proposed forms and uses, ought to be considered as
> a single sub-work-item related to container support.

I forgot to mention 13-215, which is in the paper list for 200.  Other
than its existence in that list, it does not appear in the minutes.  I
guess it got ignored.

13-215 and 14-165r1 ought to be mentioned in a "Reference:" line in the
heading for 18-265r1.