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

--- ai05s/ai05-0086-1.txt	2008/03/07 06:15:20	1.3
+++ ai05s/ai05-0086-1.txt	2008/05/10 05:14:33	1.4
@@ -1,4 +1,4 @@
-!standard 4.9.1(4/2)                                           08-01-28    AI05-0086-1/01
+!standard 4.9.1(4)                                             08-04-18    AI05-0086-1/02
 !class binding interpretation 08-01-28
 !status ARG Approved  8-0-1  08-02-10
 !status work item 08-01-28
@@ -10,7 +10,8 @@
 
 !summary
 
-(See subject.)
+The definition of statically compatible in 4.9.1 needs to take null
+exclusions into account.
 
 !question
 
@@ -19,7 +20,7 @@
 
 !recommendation
 
-(See subject.)
+(See summary.)
 
 !wording
 
@@ -57,8 +58,8 @@
 constraint is compatible with the subtype. A constraint is @i<statically
 compatible> with an access or composite subtype if it statically matches
 the constraint of the subtype, or if the subtype is unconstrained. 
-One subtype is statically compatible with a second subtype if the
-constraint of the first is @i<statically compatible> with the second
+One subtype is @i<statically compatible> with a second subtype if the
+constraint of the first is statically compatible with the second
 subtype.
 @dby
 A constraint is @i<statically compatible> with a scalar subtype if it statically
@@ -66,8 +67,8 @@
 constraint is compatible with the subtype. A constraint is @i<statically
 compatible> with an access or composite subtype if it statically matches
 the constraint of the subtype, or if the subtype is unconstrained. 
-One subtype is statically compatible with a second subtype if the
-constraint of the first is @i<statically compatible> with the second
+One subtype is @i<statically compatible> with a second subtype if the
+constraint of the first is statically compatible with the second
 subtype, and in the case of an access type, if the second subtype
 excludes null, then so does the first.