CVS difference for ais/ai-presentation.txt

Differences between 1.8 and version 1.9
Log of other versions for file ais/ai-presentation.txt

--- ais/ai-presentation.txt	2000/12/07 03:49:45	1.8
+++ ais/ai-presentation.txt	2001/05/11 03:46:21	1.9
@@ -1316,6 +1316,162 @@
 
 ****************************************************************
 
+From: Dan Eilers
+Sent: Tuesday, November 21, 2000 8:53 PM
+
+!topic typo in revised RM
+!reference RM95-9.6(26/1)
+!discussion
+
+There is an extra space after "Year" in 9.6(26/1)
+
+# This exception is also raised by the functions Year , Month, Day, and
+# Seconds and the procedure Split if the year number of the given date
+# is outside of the range of the subtype Year_Number.
+
+****************************************************************
+
+From: Randy Brukardt
+Sent: Wednesday, December 6, 2000 8:53 PM
+
+The discussion saved in AC-00002 points out that the conversions mentioned in
+paragraphs 3.5.4(9), 3.5.7(11), and 3.5.9(14, 16) are not "implicit
+conversions", as "implicit conversions" happen as part of overload resolution.
+However, these paragraphs are indexed under "implicit subtype conversion".
+Those index entries should be removed, or changed to "subtype conversion,
+neither implicit or explicit".
+
+[My solution: Add an AARM annotation to each of these paragraphs:
+
+  To be honest: The "conversion" mentioned above is not an implicit subtype
+  conversion (which is something that happens at overload resolution, see
+  4.6). Therefore, the freezing rules are not invoked on the type (which is
+  important so that representation items can be given for the type).
+  {Index: subtype conversion, neither implicit or explicit}
+
+Delete the existing index entry. (The result is that the RM would not index
+these paragraphs, while the AARM would have this funny index entry.)]
+
+****************************************************************
+
+From: Randy Brukardt (Editor)
+Date: March 22, 2001
+
+(From an FRT discussion:) The error (in 7.6.1(16/1)) is in the merged RM, where
+I failed to include the change of "operation" to "statement". Keep in mind that
+the merged RM is unofficial; the Corrigendum is the official document. If in
+doubt, look at the source. Sigh.
+
+****************************************************************
+
+From: Dirk Craeynest
+Sent: Thursday, April 05, 2001 10:07 AM
+
+!topic Still alligators in RM95 Index
+!reference RM95-Index;pp.535+543 (with COR.1:2000)
+!from Dirk Craeynest 01-04-05
+!discussion
+
+Although this was already reported during the 9X project, "ISO/IEC
+8652:1995(E) with COR.1:2000" still has two alligators hiding in the
+Index.
+
+A copy of the old report:
+
+= !topic remove alligators from RM9X Index
+= !reference RM9X-Index;5.7
+= !reference 93-3416.a Stef Van Vlierberghe  93-12-8
+= !reference 94-4515.a Dan Eilers  94-7-25
+= !from Dan Eilers 94-11-05
+= <<reference as: 94-5000.b Bob Duff 94-11-8>>
+= !discussion
+=
+= >constructor
+= >   See initialized alligator   4.8(4)
+=
+= >heap management
+= >   See also alligator   4.8(1)
+=
+= -- Dan Eilers
+
+As far as I can see on the http://www.ada-auth.org/ais.html site there
+is no reference anymore to this in the current Ada Issues Database.
+
+****************************************************************
+
+From: Randy Brukardt
+Sent: Thursday, April 05, 2001 2:01 PM
+
+The comment you reference predates the Ada 95 ARG, so of course it is not
+included in any AI.
+
+Since my mind-reading helmet is in the shop, I failed to notice and fix this
+problem. I only spent time fixing problems I knew about.
+
+I've added this to the presentation issues AI, so might get handled next
+time.
+
+****************************************************************
+
+From: Robert A Duff
+Sent: Thursday, April 05, 2001 4:20 PM
+
+> Although this was already reported during the 9X project, "ISO/IEC
+> 8652:1995(E) with COR.1:2000" still has two alligators hiding in the
+> Index.
+
+A history lesson:
+
+*I* put those "alligators" in the index, and I deliberately ignored Dan
+Eilers' gripe about it during the 9X design.  The Swiss DR's then
+complained that if alligators are in the index, then squirrels should
+be, too, so I obliged (only in the AARM).  In response to their
+complaint, I added this to the AARM index:
+
+squirrel away
+   included in fairness to alligators   8.5.4(8)
+
+which refers to:
+
+        8.g   Thus a renaming allows one to squirrel away a copy of an
+        inherited or predefined subprogram before later overriding it.
+        {squirrel away (included in fairness to alligators)}
+
+A pre-1983 Ada compiler at Intermetrics (written in Simula-67) had a
+data type called Alligator_Exp to represent "new ...", and that's where
+I got the idea for this silly joke.
+
+The Index is not "normative", and can therefore contain jokes.
+So don't go erasing my jokes, no matter how unfunny they may be.
+
+****************************************************************
+
+From: Randy Brukardt
+Sent: Thursday, April 05, 2001 4:41 PM
+
+The problem here is that these references are in place of "allocators", not
+in addition to them. So they are potentially harmful on that basis (there
+isn't a reference to allocators at either of these points in the index).
+
+****************************************************************
+
+From: Michael Yoder
+Sent: Friday, April 06, 2001 1:01 PM
+
+So, you're saying this could come back to bite us?
+
+****************************************************************
+
+
+From: Randy Brukardt (Editor)
+Date: April 6, 2001
+
+Items below this item have *not* been handled in the updated AARM or RM.
+That can be accomplished at a future time. (This second line reflects the
+"Springer" version of the documents.)
+
+****************************************************************
+
 !section 4.5.2(37)
 !subject Illegal string comparison in RM95-4.5.2 example
 !reference RM95-4.5.2(37)
@@ -1363,44 +1519,6 @@
 and as a minimum it would be useful if a short explanation
 was inserted here along the lines of that given in the
 Rationale.
-
-****************************************************************
-
-From: Dan Eilers
-Sent: Tuesday, November 21, 2000 8:53 PM
-
-!topic typo in revised RM
-!reference RM95-9.6(26/1)
-!discussion
-
-There is an extra space after "Year" in 9.6(26/1)
-
-# This exception is also raised by the functions Year , Month, Day, and
-# Seconds and the procedure Split if the year number of the given date
-# is outside of the range of the subtype Year_Number.
-
-****************************************************************
-
-From: Randy Brukardt
-Sent: Wednesday, December 6, 2000 8:53 PM
-
-The discussion saved in AC-00002 points out that the conversions mentioned in
-paragraphs 3.5.4(9), 3.5.7(11), and 3.5.9(14, 16) are not "implicit
-conversions", as "implicit conversions" happen as part of overload resolution.
-However, these paragraphs are indexed under "implicit subtype conversion".
-Those index entries should be removed, or changed to "subtype conversion,
-neither implicit or explicit".
-
-[My solution: Add an AARM annotation to each of these paragraphs:
-
-  To be honest: The "conversion" mentioned above is not an implicit subtype
-  conversion (which is something that happens at overload resolution, see
-  4.6). Therefore, the freezing rules are not invoked on the type (which is
-  important so that representation items can be given for the type).
-  {Index: subtype conversion, neither implicit or explicit}
-
-Delete the existing index entry. (The result is that the RM would not index
-these paragraphs, while the AARM would have this funny index entry.)]
 
 ****************************************************************
 

Questions? Ask the ACAA Technical Agent