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

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

--- ai12s/ai12-0275-1.txt	2018/06/16 00:57:06	1.4
+++ ai12s/ai12-0275-1.txt	2018/07/06 05:25:14	1.5
@@ -1,6 +1,8 @@
 !standard 8.5.1(2/3)                                  18-06-14  AI12-0275-1/02
 !standard 8.5.1(3/2)
 !class Amendment 18-05-10
+!status Amendment 1-2012 18-07-05
+!status ARG Approved 7-0-0  18-06-24
 !status work item 18-05-10
 !status received 17-10-15
 !priority Low
@@ -55,6 +57,51 @@
 One doesn't want to make the access_definition optional; it's
 a new type and we don't want to be declaring types implicitly.
 
+This will make renamings easier to read when the renamed object is a type
+conversion or qualified expression -- the type name is completely redundant in
+those cases.
+
+!corrigendum 8.5.1(2/3)
+
+@drepl
+@xcode<@fa<object_renaming_declaration ::=
+    defining_identifier : [null_exclusion] subtype_mark >@ft<@b<renames> @i<object_>>@fa<name
+       [aspect_specification];
+  | defining_identifier : access_definition >@ft<@b<renames> @i<object_>>@fa<name
+       [aspect_specification];>>
+@dby
+@xcode<@fa<object_renaming_declaration ::=
+    defining_identifier [: [null_exclusion] subtype_mark] >@ft<@b<renames> @i<object_>>@fa<name
+       [aspect_specification];
+  | defining_identifier : access_definition >@ft<@b<renames> @i<object_>>@fa<name
+       [aspect_specification];>>
+
+!corrigendum 8.5.1(3/2)
+
+@drepl
+The type of the @i<object_>@fa<name> shall resolve to the type determined by the
+@fa<subtype_mark>, or in the case where the type is defined by an
+@fa<access_definition>, to an anonymous access type. If the anonymous access
+type is an access-to-object type, the type of the @i<object_>@fa<name>
+shall have the same designated type as that of the
+@fa<access_definition>. If the anonymous access
+type is an access-to-subprogram type, the type of the @i<object_>@fa<name>
+shall have a designated profile that is type conformant with that of the
+@fa<access_definition>.
+@dby
+The type of the @i<object_>@fa<name> shall resolve to the type determined by the
+@fa<subtype_mark>, if present. If no @fa<subtype_mark> or @fa<access_definition>
+is present, the expected type of the @i<object_>@fa<name> is any type.
+
+In the case where the type is defined by an @fa<access_definition>, the type of the
+@i<object_>@fa<name> shall resolve to an anonymous access type. If the anonymous
+access type is an access-to-object type, the type of the @i<object_>@fa<name>
+shall have the same designated type as that of the
+@fa<access_definition>. If the anonymous access
+type is an access-to-subprogram type, the type of the @i<object_>@fa<name>
+shall have a designated profile that is type conformant with that of the
+@fa<access_definition>.
+
 !ASIS
 
 [Not sure. It might be necessary to remove/make optional access to the
@@ -174,6 +221,13 @@
 
 Here R has the same anonymous access type as P. The explicit case S has 
 different (but matching) types.
+
+****************************************************************
+
+From: RaphaŽl Amiard
+Sent: Friday, June 22, 2018  3:23 AM
+
+Thanks Randy for the update! See you this afternoon :)
 
 ****************************************************************
 

Questions? Ask the ACAA Technical Agent