CVS difference for ais/ai-00117.txt

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

--- ais/ai-00117.txt	1999/09/16 20:40:29	1.8
+++ ais/ai-00117.txt	1999/10/08 23:41:05	1.9
@@ -1,5 +1,6 @@
-!standard 03.09.02 (10)                               99-09-15  AI95-00117/06
+!standard 03.09.02 (10)                               99-10-07  AI95-00117/07
 !standard 06.03.01 (13)
+!standard 13.01    (11)
 !standard B.01     (28)
 !class binding interpretation 96-04-04
 !status Corrigendum 2000 99-07-27
@@ -152,7 +153,10 @@
 An explicitly declared dispatching operation shall not be of convention
 Intrinsic.
 
+Add a sentence to 13.1(11):
 
+Representation aspects of a partial view are the same as those of the full view.
+
 !discussion
 
 1. The default convention ought to be Ada for any entity not covered by
@@ -260,7 +264,17 @@
 incompatibility for existing code.
 
 - ----------------
+2.c. The convention of a partial view
+
+As mentioned previously, the current rules of the standard require that
+the convention be specified on the full view. So, what is the convention of
+a partial view? It is clear that a partial view and full view must have the
+same representation (including convention), since they are just views of the
+same entity. However, while this is obvious, it is also not mentioned in the
+standard. A statement to this effect needs to be added to 13.1.
 
+- ----------------
+
 3. Clearly, an implicitly declared dispatching "/=" should not
 automatically be illegal.
 
@@ -351,12 +365,24 @@
 @dinsa
 @xbullet<The default calling convention is @i<entry> for an entry.>
 @dinst
-@xbullet<If not listed above, the calling convention for any inherited
-or overriding dispatching operation of a tagged type is that
+@xbullet<If not specified above as Intrinsic, the calling convention for
+any inherited or overriding dispatching operation of a tagged type is that
 of the corresponding subprogram of the parent type. The
 default calling convention for a new dispatching operation
-of a tagged type is the convention of the full view of the type.>
+of a tagged type is the convention of the type.>
 
+!corrigendum 13.01(11)
+
+@drepl
+Representation aspects of a generic formal parameter are the same as
+those of the actual. A type-related representation item is not allowed for a
+descendant of a generic formal untagged type.
+@dby
+Representation aspects of a generic formal parameter are the same as
+those of the actual. Representation aspects of a partial view are the same
+as those of the full view. A type-related representation item is not allowed
+for a descendant of a generic formal untagged type.
+
 !corrigendum B.01(28)
 
 @drepl
@@ -568,7 +594,18 @@
 natural fall-out of implicit inheritance of Convention from types, as I
 understood the cited alternative solution suggested at the meeting ?)
 
+****************************************************************
 
+From: Randy Brukardt, October 7, 1999
 
+At the recent ARG meeting, the question was raised whether the representation
+of a partial view is defined. The AI asks this question in the restricted case
+of Convention. It is "obvious" that a partial view should have
+the same representation characteristics as the full view (convention, for
+instance), but the standard is silent.
+
+The wording as proposed by the AI does not cover this hole. Therefore, it was
+decided to add a line covering this case, which simplifies the wording
+elsewhere in this AI.
 
 ****************************************************************

Questions? Ask the ACAA Technical Agent