CVS difference for ai05s/ai05-0111-1.txt

Differences between 1.2 and version 1.3
Log of other versions for file ai05s/ai05-0111-1.txt

--- ai05s/ai05-0111-1.txt	2008/08/14 03:47:40	1.2
+++ ai05s/ai05-0111-1.txt	2008/08/14 03:50:02	1.3
@@ -1,4 +1,4 @@
-!standard  4.8(2)                                       08-08-08    AI05-0111-1/01
+!standard  4.8(2)                                       08-08-13    AI05-0111-1/02
 !standard  4.8(3/2)
 !standard  4.8(5.3/2)
 !standard  4.8(7/2)
@@ -406,6 +406,23 @@
 Perhaps we can specify the pool as an attribute, or with a
 rep clause, on the local variable.
 
+Perhaps a better approach is as follows:
+
+If a composite type is non-limited, then the accessibility level
+of the declaration of (the ultimate ancestor of) the composite type
+will determine the presumed lifetime of any object of the type.
+This allows objects of the composite type to be freely interassigned
+without having to recheck accessibility.  Any accessibility checks
+are performed when assigning to an access value component of such
+a composite object, presuming the object will ultimately be assigned
+to an object that lives at the same level as the composite type.
+
+On the other hand, if a composite type is limited, then no composite
+assignments are possible, and each object of the type is created
+in its final resting place, so the accessibility level is known,
+and can be checked when an assignment is performed to an access value
+component.
+
 !example
 
 
@@ -3685,5 +3702,15 @@
 Subject: [ARG] Persistent storage pools; E.2.1(7/1)
 
 [Editor's note: These threads are filed in this AI.]
+
+****************************************************************
+
+From: Tucker Taft
+Sent: Friday, June 13, 2008  2:48 PM
+
+I had some better ideas on how to deal with "subpool"
+access values that are components.  See below.
+
+[This is version /02 of the AI - Editor.]
 
 ****************************************************************

Questions? Ask the ACAA Technical Agent