CVS difference for ai12s/ai12-0121-1.txt

Differences between 1.1 and version 1.2
Log of other versions for file ai12s/ai12-0121-1.txt

--- ai12s/ai12-0121-1.txt	2014/08/12 00:58:20	1.1
+++ ai12s/ai12-0121-1.txt	2014/11/14 02:30:41	1.2
@@ -1,5 +1,7 @@
-!standard 13.13.2(38/3)                                14-05-14  AI05-0121-1/01
+!standard 13.13.2(38/3)                                14-11-13  AI05-0121-1/02
 !class binding interpretation 14-08-11
+!status Corrigendum 2015 14-11-13
+!status ARG Approved 7-0-1  14-10-18
 !status work item 14-08-11
 !status received 14-06-28
 !priority Medium
@@ -9,8 +11,8 @@
 !summary
 
 The stream-oriented attributes can be specified by aspect notation, and the
-same legality rules apply. Class-wide attributes can be specified as
-any concrete subprogram for interfaces.
+same legality rules apply. Class-wide attributes for interfaces can be
+specified as any nonabstract subprogram.
 
 !question
 
@@ -37,14 +39,14 @@
 
 The stream-oriented attributes may be specified for any type via an
 attribute_definition_clause. {Redundant[Alternatively, each of the specific
-stream attributes can be specified using an aspect_specification on any
-type_declaration, with the aspect name being the corresponding attribute
+stream-oriented attributes may be specified using an aspect_specification on
+any type_declaration, with the aspect name being the corresponding attribute
 name.]}
 
 [Editor's note: See the discussion as to why we only talk about specific
 stream attributes in the new text.]
 
-AARM Proof: 13.1.1 says that all operational attributes that can be specified
+AARM Proof: 13.1.1 says that all operational attributes can be specified
 with an aspect_specification.
 
 The subprogram name given in such [a clause]{an attribute_definition_clause
@@ -86,12 +88,12 @@
 @dby
 The stream-oriented attributes may be specified for any type via an
 @fa<attribute_definition_clause>. Alternatively, each of the specific
-stream attributes can be specified using an @fa<aspect_specification> on any
-@fa<type_declaration> other than an @fa<incomplete_type_declaration>, with the
-aspect name being the corresponding attribute name.
+stream-oriented attributes may be specified using an @fa<aspect_specification>
+on any @fa<type_declaration> other than an @fa<incomplete_type_declaration>,
+with the aspect name being the corresponding attribute name.
 
 The subprogram name given in such an @fa<attribute_definition_clause> or
-@fa< aspect_specification> shall statically denote a subprogram that is not an
+@fa<aspect_specification> shall statically denote a subprogram that is not an
 abstract subprogram. Furthermore, if a specific stream-oriented attribute is
 specified for an interface type, the subprogram name given in the
 @fa<attribute_definition_clause> or @fa<aspect_specification> shall statically

Questions? Ask the ACAA Technical Agent