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

--- ai05s/ai05-0091-1.txt	2008/02/26 23:36:46	1.1
+++ ai05s/ai05-0091-1.txt	2008/07/12 02:56:00	1.2
@@ -1,4 +1,10 @@
-!standard 2.3(3.1/2)                                          08-02-26    AI05-0091-1/01
+!standard 2.3(3.1/2)                                          08-07-11    AI05-0091-1/02
+!standard 2.3(4/2)
+!standard 2.3(5/2)
+!standard 2.3(5.1/2)
+!standard 2.3(5.2/2)
+!standard 2.3(5.3/2)
+!standard 2.9(2/2)
 !class binding interpretation 08-02-26
 !status work item 08-02-26
 !status received 07-10-25
@@ -77,7 +83,7 @@
 !discussion
 
 It is odd that other_format characters were ever thought to make sense in identifiers
-for Ada. By removing them now (rather than waiting for the next major revision,
+for Ada. By removing them now (rather than waiting for the next major revision),
 we reduce the possibility that anyone would write code that would depend on that
 functionality. We also simplify the language presentation.
 
@@ -105,11 +111,78 @@
 any characters that previously were allowed in identifiers but whose categories have
 changed such that they would no longer be allowed. This preserves compatibility.
 
---!corrigendum 2.3(3.1/2)
+!corrigendum 2.3(3.1/2)
 
+@drepl
+@xcode<@fa<identifier_extend ::=
+     mark_non_spacing
+   | mark_spacing_combining
+   | number_decimal
+   | punctuation_connector
+   | other_format>>
+@dby
+@xcode<@fa<identifier_extend ::=
+     mark_non_spacing
+   | mark_spacing_combining
+   | number_decimal
+   | punctuation_connector>>
+
+!corrigendum 2.3(4/2)
+
+@drepl
+After eliminating the characters in category @fa<other_format>, an
+@fa<identifier> shall not contain two consecutive characters in category
+punctuation_connector, or end with a character in that category.
+@dby
+An @fa<identifier> shall not contain two consecutive characters in
+category @fa<punctuation_connector>, or end with a character in that
+category.
+
+!corrigendum 2.3(5/2)
+
+@drepl
+Two @fa<identifier>s are considered the same if they consist of the same
+sequence of characters after applying the following transformations (in
+this order):
+@dby
+Two @fa<identifier>s are considered the same if they consist of the same
+sequence of characters after converting the characters to upper case.
+
+!corrigenum 2.3(5.1/2)
+
+@ddel
+@xbullet<The characters in category @fa<other_format> are eliminated.>
+
+!corrigendum 2.3(5.2/2)
+
+@ddel
+@xbullet<The remaining sequence of characters is converted to upper case.>
+
+!corrigendum 2.3(5.3/2)
+
+@drepl
+After applying these transformations, an @fa<identifier> shall not be identical
+to a reserved word (in upper case).
+@dby
+After converting to upper case, an @fa<identifier> shall not be identical to a
+reserved word (in upper case). 
+
+!corrigendum 2.9(2/2)
+
+@drepl
+The following are the @i<reserved words>. Within a program, some or all of the
+letters of a reserved word may be in upper case, and one or more characters in
+category @fa<other_format> may be inserted within or at the end of the reserved
+word.
+@dby
+The following are the @i<reserved words>. Within a program, some or all of the
+letters of a reserved word may be in upper case.
+
+
 !ACATS Test
 
-An ACATS C-Test could be tried.
+An ACATS B-Test should be tried to see that other_format characters are not allowed
+in identifiers.
 
 !appendix