CVS difference for ais/ai-00363.txt

Differences between 1.6 and version 1.7
Log of other versions for file ais/ai-00363.txt

--- ais/ai-00363.txt	2004/07/27 23:01:06	1.6
+++ ais/ai-00363.txt	2004/11/14 06:37:20	1.7
@@ -1,11 +1,10 @@
-!standard  03.03.1(9)                                   04-06-30  AI95-00363/04
+!standard  03.03.1(9)                                   04-11-07  AI95-00363/05
 !standard  03.06(11)
 !standard  03.07.01(7/1)
 !standard  03.10(9)
 !standard  03.10.2(26)
 !standard  03.10.2(27)
 !standard  04.06(12.1/1)
-!standard  04.06(14)
 !standard  04.06(16)
 !standard  04.08(6)
 !standard  08.05.1(5/1)
@@ -128,6 +127,7 @@
 
     ... unless this subtype is indefinite, or the variable is [aliased]
     {constrained by its initial value}.
+
 [part 2] Replace last part of 3.10.2(27) with:
 
     ... if D is untagged, then the type of the view shall be D, and either:
@@ -167,7 +167,7 @@
   AARM NOTE: If there is a constrained partial view of the type, this
     allows the objects to be unconstrained. This eliminates privacy breaking
     (we don't want the objects to act different simply because they're
-    allocated). Such a created object is effectively contrained by its initial
+    allocated). Such a created object is effectively constrained by its initial
     value if the access type is an access-to-constant type, or the designated
     type is limited (in all views), but we don't need to state that here. It is
     implicit in other rules. Note, however, that a value of an
@@ -289,11 +289,11 @@
     end Test;
 
 Because the AStr object is allocated from a storage pool, Ada 95 says that it
-is constrained by it's initial value (the null string in this case). That
+is constrained by its initial value (the null string in this case). That
 means that the attempt to assign a longer string raises Constraint_Error,
-even though the presense of the discriminants are unknown to the client.
+even though the presence of the discriminants are unknown to the client.
 The proposed changes allow unconstrained allocated objects so long as they
-have a constrained partial view (as in this example), so this anomoly is
+have a constrained partial view (as in this example), so this anomaly is
 eliminated.
 
 !corrigendum 3.3.1(9)
@@ -393,7 +393,7 @@
 @xinbull<If @i<A> is a named access type and @i<D> is a tagged type, then the
 type of the view shall be covered by @i<D>; if @i<A> is anonymous and @i<D> is
 tagged, then the type of the view shall be either @i<D>'Class or a type
-covered by @i<D>; if @i<D> is untagged, then the type of the view shall be
+covered by D; if @i<D> is untagged, then the type of the view shall be
 @i<D>, and @i<A>'s designated subtype shall either statically match the
 nominal subtype of the view or be discriminated and unconstrained;>
 @dby
@@ -416,12 +416,6 @@
 @xbullet<In a view conversion, if the target type has aliased components, then
 so shall the operand type.>
 
-!corrigendum 4.06(14)
-
-@ddel
-@xbullet<If the target type is an access-to-variable type, then the operand
-type shall be an access-to-variable type;>
-
 !corrigendum 4.06(16)
 
 @drepl
@@ -436,9 +430,6 @@
 unconstrained in any partial view, and the target designated
 subtype shall be unconstrained;>
 
-@xbullet<If the target type is an access-to-variable type, then the operand
-type shall be an access-to-variable type; and>
-
 !corrigendum 4.08(6)
 
 @drepl
@@ -457,7 +448,7 @@
 constrained by its initial value (even if the designated subtype is
 unconstrained with defaults).
 
-!corrigendum 8.5.1(5)
+!corrigendum 8.5.1(5/1)
 
 @drepl
 The renamed entity shall not be a subcomponent that depends on

Questions? Ask the ACAA Technical Agent