CVS difference for ai12s/ai12-0005-1.txt

--- ai12s/ai12-0005-1.txt	2020/12/09 06:23:52	1.42
+++ ai12s/ai12-0005-1.txt	2021/01/06 07:29:48	1.43
@@ -2803,6 +2803,12 @@
 
 [From the AARM Review of John Barnes (October 2020) - Editor.]
 
+10.1  9.d         Please move the commas outside the quotes. As in 10.1  9.
+
+[Editor's reply: 10.1 only goes to 4.d. There is a period inside of quotes 
+in 4.d. Ahhhh, you meant 10.1.1(9.d). These will just be fixed, as they don't 
+change any meaning.]
+
 11.4.2  23.e/5    The last part of this seems garbled at first sight. Some 
 such requirements etc. Maybe the trouble is simply that Suppressed should 
 be suppressed.
@@ -2831,9 +2837,144 @@
 
 12.3  18.g/5       "an generic instantiation" should be "a generic instantiation".
 
+12.5.1  23.a/2    I was surprised to read that Constrained is now considered obsolete.
+I see that it is in J. Maybe I need to update my book.
+I always find the phrase considered obsolete rather odd. Is the wretched thing
+obsolete or not? Do we always say "considered obsolete" rather than just
+"obsolete"? No. I searched for considered obsolete and this was the only instance
+found by Acrobat. So perhaps here we should just say obsolete.
+
+[Editor's note: The proper term is "obsolescent", there is only one other use
+of "obsolete" outside of Annex J. "Considered" is probably a noise word, but it
+is used often in the AARM, so changing for just that probably isn't worthwhile.
+But since we're changing this paragraph anyway to get rid of "obsolete", might
+as well get rid of "considered" too.]
+
+12.6  8.j/5         I would insert "as" so it reads "... to be class-wide as 
+in the following unusual case."
+
+***************************************************************
+
+From: Pascal Pignard
+Sent: Saturday, January 2, 2021  3:38 AM (privately to the editor)
+
+Hello, here is a very minor typo: double period at the end of some paragraphs:
+
+3.2 Types and Subtypes
+10.d/2      {AI95-00442-01} The set of limited types does not form a class
+            (since nonlimited types can inherit from limited interfaces), but
+            the set of nonlimited types does. The set of tagged record types
+            and the set of tagged private types do not form a class (because
+            each of them can be extended to create a type of the other
+            category); that implies that the set of record types and the set
+            of private types also do not form a class (even though untagged
+            record types and untagged private types do form a class). In all
+            of these cases, we can talk about the category of the type; for
+            instance, we can talk about the "category of limited types"..
+
+3.9 Tagged Types and Type Extensions
+26.b/3      Implementation Advice: Tags.Internal_Tag should return the tag of
+            a type, if one exists, whose innermost master is a master of the
+            point of the function call..
+
+4.2 Literals
+4/5 {AI12-0325-1} {AI12-0373-1} The expected type for a primary that is a 
+string_literal shall be a single string type or a type with a specified 
+String_Literal aspect (see 4.2.1). In either case, the string_literal is 
+interpreted to be of its expected type. If the expected type of an integer 
+literal is a type with a specified Integer_Literal aspect (see 4.2.1), the 
+literal is interpreted to be of its expected type; otherwise it is interpreted 
+to be of type universal_integer. If the expected type of a real literal is a 
+type with a specified Real_Literal aspect (see 4.2.1), it is interpreted to be
+of its expected type; otherwise, it is interpreted to be of type 
+universal_real..
+
+11.5 Suppressing Checks
+1/2 {AI95-00224-01} Checking pragmas give instructions to an implementation on 
+handling language-defined checks. A pragma Suppress gives permission to an 
+implementation to omit certain language-defined checks, while a pragma 
+Unsuppress revokes the permission to omit checks..
+
+13.7.1 The Package System.Storage_Elements
+11.c/2      Implementation defined: The range of
+            Storage_Elements.Storage_Offset, the modulus of
+            Storage_Elements.Storage_Element, and the declaration of
+            Storage_Elements.Integer_Address..
+
+A.1 The Package Standard
+56.k/2      {8652/0028} {AI95-00145-01} Corrigendum: Corrected the parameter
+            type for the Boolean operators declared in Standard..
+
+A.4.4 Bounded-Length String Handling
+101/1       {8652/0049} {AI95-00128-01} {AI95-00238-01} Returns the slice at
+            positions Low through High in the string represented by Source;
+            propagates Index_Error if Low > Length(Source)+1 or High >
+            Length(Source). The bounds of the returned string are Low and
+            High..
+
+A.18.20 The Generic Package Containers.Bounded_Doubly_Linked_Lists
+11/5        Returns a list whose elements have the same values as the elements
+            of Source..
+
+C.5 Aspect Discard_Names
+5/4 {AI12-0072-1} The local_name (if present) shall denote an entity with 
+runtime name text. The pragma specifies that the aspect Discard_Names for the
+type or exception has the value True. Without a local_name, the pragma
+specifies that all entities with runtime name text declared after the pragma,
+within the same declarative region have the value True for aspect
+Discard_Names. Alternatively, the pragma can be used as a configuration
+pragma. If the configuration pragma Discard_Names applies to a compilation
+unit, all entities with runtime name text declared in the compilation unit
+have the value True for the aspect Discard_Names..
+
+F.3.2 Edited Output Generation
+46  4.  Any other Character is replaced by the space character..
+
+M.3 Implementation Advice
+12/3   * Tags.Internal_Tag should return the tag of a type, if one exists,
+        whose innermost master is a master of the point of the function call..
+        See 3.9(26.1/3).
+
+I wish you and your family the best for 2021 and plenty of courage for the 
+soon coming new Ada standard ;-)
+
+***************************************************************
+
+From: Randy Brukardt
+Sent: Tuesday, January 5, 2021  9:45 PM
+
+Thanks. Double periods often occur when a period is added to the end of new 
+(inserted) text, but the original (deleted) text does not delete the ending 
+period. Most of these have be in the AARM for a long time. (It's hard to look
+for double periods as they commonly appear in ranges and slices.)
+
+Note that as punctuation corrections, these fall under the category of 
+"obvious typographical mistakes" and thus won't be marked in any way (just
+corrected).
+
+***************************************************************
+
+[From the AARM Review of Justin Squirek (October 2020) - Editor.]
+
+---------
+-- 4.7 --
+---------
+
+10.b/4: The corrigendum phrasing could be improved to be less repetitive:
+
+"...cases when this could be the case are likely to be rare (the qualified 
+expression would have to have a stricter subtype than the following usage) 
+and the check is more likely to detect bugs than be unexpected."
+
+to
+
+"...cases [where this scenario arises] are likely to be rare (the qualified 
+expression would have to have a stricter subtype than the following usage) 
+and the check is more likely to detect bugs than be unexpected."
+
 ***************************************************************
 
-Editor's note (December 8, 2020): All of the items above this
+Editor's note (January 5, 2021): All of the items above this
 marker have been included in the working version of the AARM.
 
 ****************************************************************