CVS difference for ais/ai-10359.txt

Differences between 1.2 and version 1.3
Log of other versions for file ais/ai-10359.txt

--- ais/ai-10359.txt	2004/06/25 00:55:46	1.2
+++ ais/ai-10359.txt	2004/07/27 23:01:09	1.3
@@ -1,7 +1,9 @@
-!standard 12.03     (12)                           04-04-02  AI95-00359-02/01
+!standard 12.03     (12)                           04-07-02  AI95-00359-02/02
 !standard 12.03     (20)
 !standard 13.14     (05)
 !class amendment 04-04-02
+!status work item 04-06-24
+!status ARG Approved 6-1-4  04-06-17
 !status work item 04-04-02
 !status received 04-04-02
 !priority Low
@@ -137,8 +139,8 @@
    o the next reference to a subprogram, protected subprogram, or generic unit
      declared within the instantiation;
 
-   o the next freezing point for a task or private type declared within the
-     instantiation;
+   o creation of an object of a type that does not have preelaboratable
+     initialization;
 
    o the next non-instance body;
 
@@ -830,6 +832,28 @@
 
 This seems like a fine case to consider as a pathology, and not worry about
 it. But I could be convinced outwise.
+
+****************************************************************
+
+From: Pascal Leroy
+Sent: Friday, June 25, 2004   4:32 AM
+
+Bob wondered:
+
+> I'm curious what other compilers do with it.  Is it not
+> illegal by 3.2.1(5), and does this not already break privacy
+> (causing confusion for at least two compilers)?
+
+Here is the output of Apex:
+
+11:18:27 >>> Line 15: X1 : Sub.T2;
+11:18:27 *** Sub.T2 contains a circularity [RM_95 3.2.1(5)]
+11:18:27 >>> Line 17: X : T1;
+11:18:27 *** T1 contains a circularity [RM_95 3.2.1(5)]
+
+So at least one implementer seems to agree that this is illegal by
+3.2.1(5).  And yes, it breaks privacy, but that's an absurd program, and
+the privacy breaking only occurs in a single unit.  Yawn.
 
 ****************************************************************
 

Questions? Ask the ACAA Technical Agent