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

Differences between 1.1 and version 1.2
Log of other versions for file ai05s/ai05-0016-1.txt

--- ai05s/ai05-0016-1.txt	2006/06/23 00:47:18	1.1
+++ ai05s/ai05-0016-1.txt	2006/10/10 00:52:43	1.2
@@ -193,3 +193,22 @@
 
 ****************************************************************
 
+From: Pascal Leroy
+Date: Monday, July 10, 2006  4:35 AM
+
+> I would agree with Randy that it was an oversight.
+> (others => <>) should be permitted for a null record.
+> I agree with Erhard that we had long debates about
+> allowing others => <> in general, but Randy is right
+> that we ultimately decided to allow it.  Certainly
+> the "danger" associated with others => <> is minimal
+> in the case of a null record!
+
+Just to beat a dead horse: (others => <>) should definitely be permitted,
+otherwise we have a generic contract model problem.  Consider a formal
+derived tagged type, whose ancestor is a null record.  The actual may or
+may not be a null record.  Now if in the generic body you write (others =>
+<>), is it legal or not?  Surely we don't want to assume the worst here.
+
+****************************************************************
+

Questions? Ask the ACAA Technical Agent