CVS difference for ai22s/ai22-0018-1.txt

Differences between 1.3 and version 1.4
Log of other versions for file ai22s/ai22-0018-1.txt

--- ai22s/ai22-0018-1.txt	2021/11/19 07:42:35	1.3
+++ ai22s/ai22-0018-1.txt	2022/01/28 07:06:50	1.4
@@ -1,10 +1,11 @@
-!standard 4.3.5(24/5)                                    21-11-18  AI22-0018-1/03
+!standard 4.3.5(24/5)                                    22-01-14  AI22-0018-1/04
 !standard 4.3.5(26/5)
 !standard 4.3.5(38/5)
 !standard 4.3.5(39/5)
 !standard 4.9(8.1/5)
 !standard 13.1(0.1/3)
 !class binding interpretation 21-11-12
+!status Corrigendum 1-2022 22-01-14
 !status ARG Approved 13-0-0  21-11-18
 !status work item 21-11-12
 !status received 21-11-12
@@ -130,8 +131,8 @@
 
 (3) For a discrete_range to be legal, the key type of the container type has
 to be discrete. But there is no problem describing the operation of such
-ranges, and indeed we have to do so anyway as the wording is shared with
-indexed aggregates which do allow these.
+ranges, and indeed we have to do so anyway as the (dynamic semantics) wording
+is shared with indexed aggregates which do allow these.
 
 The original author of container aggregates thinks that the restriction came
 from an early version that existed before indexed aggregates were added. That
@@ -147,6 +148,84 @@
 
 (4) When the attribute was deleted, this rule should have been removed as
 well, but obviously was not.
+
+!corrigendum 4.3.5(24/5)
+
+@drepl
+The expected type for a @fa<positional_container_aggregate> shall have an
+Aggregate aspect that includes a specification for an Add_Unnamed
+procedure or an Assign_Indexed procedure. The expected type for a
+@fa<named_container_aggregate> that contains one or more
+@fa<iterated_element_association>s with a @i<key_>@fa<expression> shall have an
+Aggregate aspect that includes a specification for the Add_Named
+procedure. The expected type for a @fa<named_container_aggregate> that
+contains one or more @fa<key_choice_list>s shall have an Aggregate aspect
+that includes a specification for the Add_Named or Assign_Indexed
+procedure. A @fa<null_container_aggregate> can be of any type
+with an Aggregate aspect.
+@dby
+The expected type for a @fa<positional_container_aggregate> shall have an
+Aggregate aspect that includes a specification for an Add_Unnamed
+procedure or an Assign_Indexed procedure. The expected type for a
+@fa<named_container_aggregate> that contains one or more
+@fa<iterated_element_association>s with a @i<key_>@fa<expression> shall have an
+Aggregate aspect that includes a specification for the Add_Named
+procedure. The expected type for a @fa<named_container_aggregate> that
+contains one or more @fa<key_choice_list>s shall have an Aggregate aspect
+that includes a specification for the Add_Named or Assign_Indexed
+procedure. For other kinds of @fa<named_container_aggregate>s, there are no
+additional restrictions on the Aggregate aspect of the expected type. A
+@fa<null_container_aggregate> can be of any type with an Aggregate aspect.
+
+!corrigendum 4.3.5(26/5)
+
+@drepl
+A @fa<container_element_association> with a <@> rather than an @fa<expression>,
+or with a @fa<key_choice> that is a @fa<discrete_range>, is permitted only in
+an indexed aggregate.
+@dby
+A @fa<container_element_association> with a <@> rather than an @fa<expression>
+is permitted only in an indexed aggregate.
+
+!corrigendum 4.3.5(38/5)
+
+@ddel
+@xinbull<for a @fa<named_container_aggregate> without an 
+@fa<iterated_element_association>, the number of @i<key_>@fa<expression>s;>
+
+!corrigendum 4.3.5(39/5)
+
+@drepl
+@xinbull<for a @fa<named_container_aggregate> where every 
+@fa<iterated_element_association> contains a @fa<loop_parameter_specification>,
+the total number of elements specified by all of the 
+@fa<container_element_association>s;>
+@dby
+@xinbull<for a @fa<named_container_aggregate> where each 
+@fa<iterated_element_association>, if any, contains a 
+@fa<loop_parameter_specification>, the total number of elements specified by
+all of the @fa<container_element_association>s;>
+
+!corrigendum 4.9(8.1/5)
+
+@ddel
+@xbullet<an @fa<attribute_reference> whose @fa<prefix> denotes a non-generic
+entity that is not declared in a generic unit, and whose
+@fa<attribute_designator> is Nonblocking;>
+
+!corrigendum 13.1(0.1/3)
+
+@drepl
+Two kinds of aspects of entities can be specified: representation aspects and 
+operational aspects. Representation aspects affect how the types and other 
+entities of the language are to be mapped onto the underlying machine. 
+Operational aspects determine other properties of entities.
+@dby
+Two kinds of aspects of entities can be specified: representation aspects and 
+operational aspects. Representation aspects affect how the types and other 
+entities of the language are to be mapped onto the underlying machine. 
+Operational aspects determine other properties of entities. When 
+not specified otherwise, an aspect is defined to be an operational aspect.
 
 !ACATS test
 

Questions? Ask the ACAA Technical Agent