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

Differences between 1.3 and version 1.4
Log of other versions for file ai12s/ai12-0106-1.txt

--- ai12s/ai12-0106-1.txt	2014/10/14 01:29:30	1.3
+++ ai12s/ai12-0106-1.txt	2014/11/14 02:30:41	1.4
@@ -1,6 +1,8 @@
-!standard 13.1.1(28/3)                                 14-10-13  AI05-0106-1/03
+!standard 13.1.1(28/3)                                 14-11-13  AI05-0106-1/04
 !standard 13.13.2(38/3)
 !class binding interpretation 14-05-14
+!status Corrigendum 2015 14-11-13
+!status ARG Approved 7-0-1  14-10-18
 !status work item 14-05-14
 !status received 14-04-25
 !priority Medium
@@ -38,7 +40,7 @@
 
 !wording
 
-[Editor's note: The below wording assumes that the changes of AI12-0106-1
+[Editor's note: The below wording assumes that the changes of AI12-0121-1
 are adopted. Note that 13.13.2(38/3) is split into two paragraphs, and
 we only modify the first.]
 
@@ -51,21 +53,22 @@
 
   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
+  specific stream-oriented attributes may be specified using an
   aspect_specification on any type_declaration, with the aspect name
-  being the corresponding attribute name.] Each of the class-wide stream
-  attributes can be specified for a tagged type T using the name of the
-  stream attribute followed by 'Class; such class-wide aspects do not
-  apply to other descendants of T.}
+  being the corresponding attribute name.] Each of the class-wide
+  stream-oriented attributes may be specified using an aspect_specification
+  for a tagged type T using the name of the stream-oriented attribute
+  followed by 'Class; such class-wide aspects do not apply to other
+  descendants of T.}
 
-    AARM Reason: We need the last sentence to override the blanket rule
-    given in 13.1.1 that aspect'Class applies to the type and all
+    AARM Reason: We need the last part of the last sentence to override
+    the blanket rule given in 13.1.1 that aspect'Class applies to the type and all
     descendants.
 
 [Yet another Editor's note: Add Aspect Descriptions for Read'Class, Write'Class,
 and so on after the existing ones. Probably move the existing ones up below the
-above paragraph, the other existing AARM notes will follow the split paragraph
-below.]
+above paragraph, the other existing AARM notes will follow the second half of
+the split paragraph.]
 
 !discussion
 
@@ -90,7 +93,7 @@
 @drepl
 If the @fa<aspect_mark> includes 'Class, then:
 @dby
-If the aspect_mark includes 'Class (a @i<class-wide aspect>), then,
+If the @fa<aspect_mark> includes 'Class (a @i<class-wide aspect>), then,
 unless specified otherwise for a particular class-wide aspect:
 
 !corrigendum 13.13.2(38/3)
@@ -105,18 +108,20 @@
 @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
-aspect_specification on any type_declaration, with the aspect name
-being the corresponding attribute name. Each of the class-wide stream
-attributes can be specified for a tagged type @i<T> using the name of the
-stream attribute followed by 'Class; such class-wide aspects do not
+specific stream-oriented attributes may be specified using an
+@fa<aspect_specification> on any @fa<type_declaration>, with the aspect name
+being the corresponding attribute name. Each of the class-wide stream-oriented
+attributes may be specified using an
+@fa<aspect_specification> for a tagged type @i<T> using the name of the
+stream-oriented attribute followed by 'Class; such class-wide aspects do not
 apply to other descendants of @i<T>.
 
-The subprogram name given in such a clause
-shall statically denote a subprogram that is not an abstract subprogram.
-Furthermore, if a stream-oriented attribute is specified for an interface type
-by an @fa<attribute_definition_clause>, the subprogram name given in the
-clause shall statically denote a null procedure.
+The subprogram name given in such an @fa<attribute_definition_clause> or
+@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
+denote a null procedure.
 
 !ASIS
 

Questions? Ask the ACAA Technical Agent