CVS difference for ais/ai-00406.txt

Differences between 1.1 and version 1.2
Log of other versions for file ais/ai-00406.txt

--- ais/ai-00406.txt	2005/02/08 01:12:05	1.1
+++ ais/ai-00406.txt	2005/03/09 00:47:47	1.2
@@ -1,6 +1,8 @@
-!standard 3.3.1(2)                                     05-02-05  AI95-00406/01
+!standard 3.3.1(2)                                     05-03-08  AI95-00406/02
 !standard 3.6(7)
 !class amendment 05-02-05
+!status Amendment 200Y 05-03-08
+!status ARG Approved 9-0-0  05-02-12
 !status work item 05-02-05
 !status received 05-02-05
 !priority High
@@ -51,8 +53,6 @@
 of orthogonality suggest this should be possible and there seem no
 reasons why they should not.
 
-Remember that access parameters are implicitly considered to be aliased.
-
 This would allow
 
    type TT is ...
@@ -69,8 +69,31 @@
 !example
 
 (See discussion.)
+
+!corrigendum 3.3.1(2)
 
---!corrigendum
+@drepl
+@xcode<@fa<object_declaration ::=
+   defining_identifier_list : [>@ft<@b<aliased>>@fa<] [>@ft<@b<constant>>@fa<] subtype_indication [:= expression]
+ | defining_identifier_list : [>@ft<@b<aliased>>@fa<] [>@ft<@b<constant>>@fa<] array_type_definition [:= expression]
+ | single_task_declaration
+ | single_protected_declaration>>
+@dby
+@xcode<@fa<object_declaration ::=
+   defining_identifier_list : [>@ft<@b<aliased>>@fa<] [>@ft<@b<constant>>@fa<] subtype_indication [:= expression]
+ | defining_identifier_list : [>@ft<@b<aliased>>@fa<] [>@ft<@b<constant>>@fa<] access_definition [:= expression]
+ | defining_identifier_list : [>@ft<@b<aliased>>@fa<] [>@ft<@b<constant>>@fa<] array_type_definition [:= expression]
+ | single_task_declaration
+ | single_protected_declaration>>
+
+!corrigendum 3.6(7)
+
+@drepl
+@xcode<@fa<component_definition ::= [>@ft<@b<aliased>>@fa<] subtype_indication>>
+@dby
+@xcode<@fa<component_definition ::=
+   [>@ft<@b<aliased>>@fa<] subtype_indication
+ | [>@ft<@b<aliased>>@fa<] access_definition>>
 
 !ACATS test
 

Questions? Ask the ACAA Technical Agent