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

--- ai05s/ai05-0214-1.txt	2010/08/20 04:07:17	1.3
+++ ai05s/ai05-0214-1.txt	2010/12/15 00:10:59	1.4
@@ -1,4 +1,4 @@
-!standard  3.7(9.1/2)                                10-08-04  AI05-0214-1/02
+!standard  3.7(9.1/2)                                10-11-22  AI05-0214-1/03
 !standard  3.7.2(3)
 !class amendment 10-06-12
 !status work item 10-06-12
@@ -43,13 +43,15 @@
 
 A'Constrained
     Yields the value True if A denotes a constant, a value, [or] a constrained
-    variable{, or a tagged object}, and False otherwise.
+    variable{, or is known to be constrained}, and False otherwise.
 
-AARM Reason: Tagged objects always are considered constrained by this attribute
-to avoid distributed overhead for parameters of limited classwide types, as
-limited tagged objects may technically be unconstrained if they use defaulted
-discriminants. Such objects still cannot have their discriminants changed, as
-assignment is not supported for them, so there is no use for this attribute
+AARM Reason: Objects that are known to be constrained, which include all tagged
+objects (as nonlimited tagged types cannot have discriminant defaults, 
+and limited tagged objects are immutably limited) always are considered constrained
+by this attribute to avoid distributed overhead for parameters of limited classwide
+types, as limited tagged objects may technically be unconstrained if they use
+defaulted discriminants. Such objects still cannot have their discriminants changed,
+as assignment is not supported for them, so there is no use for this attribute
 that would justify the overhead of passing it with all classwide parameters.
 
 !discussion
@@ -67,8 +69,8 @@
 and thus the value of 'Constrained would have to be passed with the parameter.
 Since 'Constrained is not useful for limited types, this is pointless.
 
-Thus we 'Constrained to be True for all tagged objects, regardless of the form of
-their discriminants. We considered a more consistent rule which would 
+Thus we define 'Constrained to be True for all tagged objects, regardless of
+the form of their discriminants. We considered a more consistent rule which would 
 define objects of nonformal limited tagged types to be constrained
 by their initial value, but it required too many wording changes for a "simple"
 change.
@@ -83,6 +85,11 @@
 !ACATS test
 
 Create an ACATS C-Test(s) to check this feature.
+
+!ASIS
+
+There is no impact on ASIS, but ASIS users may need to take into account the new
+possibility of getting default discriminants for a limited tagged type.
 
 !appendix