CVS difference for ais/ai-00231.txt

Differences between 1.23 and version 1.24
Log of other versions for file ais/ai-00231.txt

--- ais/ai-00231.txt	2005/08/21 06:00:16	1.23
+++ ais/ai-00231.txt	2005/10/31 05:18:13	1.24
@@ -1,4 +1,4 @@
-!standard  3.10      (06)                        05-07-11  AI95-00231/16
+!standard  3.10      (06)                        05-09-20  AI95-00231/17
 !standard  3.2       (07)
 !standard  3.2       (08)
 !standard  3.2.2     (03)
@@ -514,6 +514,7 @@
 @xcode<@fa<access_definition ::= >@ft<@b<access>>@fa< subtype_mark>>
 @dby
 @xcode<@fa<null_exclusion ::= >@ft<@b<not null>>
+
 @fa<access_definition ::=
    [null_exclusion] >@ft<@b<access>>@fa< [general_access_modifier] subtype_mark>>
 
@@ -571,12 +572,6 @@
 @dinst
 @i<@s8<Legality Rules>>
 
-A @fa<null_exclusion> is only allowed in a @fa<subtype_indication>,
-@fa<discriminant_specification>, @fa<parameter_specification>,
-@fa<parameter_and_result_profile>, @fa<object_renaming_declaration>, or
-@fa<formal_object_declaration> if the @fa<subtype_mark> in the construct
-denotes an access subtype that does not exclude null.
-
 If a @fa<subtype_indication>, @fa<discriminant_specification>,
 @fa<parameter_specification>, @fa<parameter_and_result_profile>,
 @fa<object_renaming_declaration>, or @fa<formal_object_declaration> has a
@@ -723,10 +718,10 @@
 !corrigendum 7.4(7)
 
 @drepl
-@xbullet<If deferred constant declaration includes the reserved word
+@xbullet<If the deferred constant declaration includes the reserved word
 @b<aliased>, then the full declaration shall also.>
 @dby
-@xbullet<If deferred constant declaration includes the reserved word
+@xbullet<If the deferred constant declaration includes the reserved word
 @b<aliased>, then the full declaration shall also;>
 
 @xbullet<If the subtype of the deferred constant declaration excludes null, the
@@ -1019,6 +1014,59 @@
 That's always preferrable, but it wouldn't have helped in this case, because
 I didn't actually send the changes up until I saw your note. So only people
 who were at the meeting had the new version.
+
+*************************************************************
+
+From: Christoph Grein
+Sent: Monday, February 21, 2005  2:18 AM
+
+Replace paragraph 11: [AI95-00231-01]
+
+When evaluating a dereference (explicit or implicit), check that the
+value of the name is not null. When passing an actual parameter to a
+formal access parameter, check that the value of the actual parameter is
+not null. When evaluating a discriminant_association for an access
+discriminant, check that the value of the discriminant is not null.
+
+by:
+
+When evaluating a dereference (explicit or implicit), check that the
+value of the name is not null. When converting to a null-excluding
+subtype, check that the converted value is not null.
+-----
+Since from paragraph 4, name was removed, the replacement text seems
+incorrect. Such a text would belong to J.10.
+
+*************************************************************
+
+From: Randy Brukardt
+Sent: Monday, February 21, 2005  2:31 PM
+
+Could you reference the section in question; you didn't mention it, and
+there is no other context to your note, so this could be anywhere in the 250
+pages. As it is, your note is totally incomprehensible (what was changed in
+what paragraph 4?).
+
+*************************************************************
+
+From: Christoph Grein
+Sent: Tuesday, February 22, 2005 12:41 AM
+
+I'm so sorry, I just realised my mistake. It's 11.5 Suppressing Checks.
+
+*************************************************************
+
+From: Randy Brukardt
+Sent: Wednesday, October 19, 2005  7:11 PM
+
+(Replying to an old comment:)
+
+> Since from paragraph 4, name was removed, the replacement text seems
+> incorrect. Such a text would belong to J.10.
+
+No, the wording is correct. "name" in this paragraph refers to the name that
+comprises the dereference. It has absolutely nothing to do with the name that
+used to appear in pragma Suppress (that's now in J.10).
 
 *************************************************************
 

Questions? Ask the ACAA Technical Agent