CVS difference for ais/ai-00240.txt
--- ais/ai-00240.txt 2001/10/19 01:36:44 1.3
+++ ais/ai-00240.txt 2002/05/25 03:42:18 1.4
@@ -1,8 +1,9 @@
-!standard E.2.2 (8) 01-10-17 AI95-00240/03
+!standard E.2.2 (8) 02-05-09 AI95-00240/04
!standard E.2.2 (14)
!standard E.2.3 (14)
!class binding interpretation 00-10-04
-!status ARG approved 7-0-1 01-10-07
+!status Amendment 200Y 02-05-09
+!status ARG Approved 7-0-1 01-10-07
!status work item 00-10-04
!status received 00-10-04
!reference AI95-00195
@@ -18,7 +19,7 @@
!question
-The Technical Corrigendum changes 13.13.2(36/1) to allow calls to stream
+The Technical Corrigendum changed 13.13.2(36/1) to allow calls to stream
attributes for limited type extensions where the attribute was specified for
an ancestor type:
@@ -38,7 +39,7 @@
!wording
-AI95-00195 makes a further change in 13.13.1(36), introducing the idea of
+AI95-00195 makes a further change in 13.13.2(36/1), introducing the idea of
a stream-oriented attribute being "available". This change makes it easier
to word the replacement paragraphs.
@@ -46,11 +47,11 @@
attribute_definition_clause" as "user-specified attribute" is not defined and
ignores visibility issues.
-Change E.2.2(14) to say "each non-controlling formal parameter shall have
+Change E.2.2(14/1) to say "each non-controlling formal parameter shall have
either a nonlimited type or a type with available Read and Write stream
attributes;"
-Change E.2.3(14) to say "...or a formal parameter of a limited type unless
+Change E.2.3(14/1) to say "...or a formal parameter of a limited type unless
that limited type has available Read and Write stream attributes;"
!discussion
@@ -79,10 +80,10 @@
attribute_definition_clause;
The intent of this paragraph is that the attributes be available (see the
-Defect Report 8652/0083 for a discussion). Thus, it echos the original
-13.13.2(36). However, with the change to 13.13.2(36), this does not allow
+Defect Report 8652/0083 for a discussion). Thus, it echoes the original
+13.13.2(36/1). However, with the change to 13.13.2(36/1), this does not allow
the use of type whose attributes were specified for an ancestor type. Thus,
-this should be changed to match 13.13.2(36).
+this should be changed to match 13.13.2(36/1).
E.2.3(14/1) says:
it shall not be, nor shall its visible part contain, a subprogram (or
@@ -90,7 +91,7 @@
a formal parameter of a limited type unless that limited type has
user-specified Read and Write attributes;
-This paragraph has the same intent as E.2.2(14). Thus, the wording should be
+This paragraph has the same intent as E.2.2(14/1). Thus, the wording should be
similar.
!corrigendum E.2.2(8)
@@ -107,7 +108,7 @@
subcomponent, shall have Read and Write attributes specified by a visible
@fa<attribute_definition_clause>.>
-!corrigendum E.2.2(14)
+!corrigendum E.2.2(14/1)
@drepl
@xbullet<The primitive subprograms of the corresponding specific limited
private type shall only have access parameters if they are controlling formal
@@ -119,9 +120,9 @@
private type shall only have access parameters if they are controlling formal
parameters; each non-controlling formal parameter shall have either a
nonlimited type or a type with available Read and Write attributes
-(see 13.13.1);>
+(see 13.13.2);>
-!corrigendum E.2.3(14)
+!corrigendum E.2.3(14/1)
@drepl
@xbullet<it shall not be, nor shall its visible part contain, a subprogram
(or access-to-subprogram) declaration whose profile has an access
@@ -131,7 +132,7 @@
@xbullet<it shall not be, nor shall its visible part contain, a subprogram
(or access-to-subprogram) declaration whose profile has an access
parameter, or a formal parameter of a limited type unless that limited
-type has available Read and Write attributes (see 13.13.1);>
+type has available Read and Write attributes (see 13.13.2);>
!ACATS test
@@ -179,7 +180,7 @@
attribute_definition_clause;
The intent of this paragraph is that the attributes be callable (see the
-Defect Report 8652/0083 for a discussion). Thus, it echos the original
+Defect Report 8652/0083 for a discussion). Thus, it echoes the original
13.13.2(36). However, with the change to 13.13.2(36), this does not allow
the use of type whose attributes were specified for an ancestor type. It
seems that this should be changed to match 13.13.2(36). [If that is done, it
Questions? Ask the ACAA Technical Agent