CVS difference for ais/ai-00097.txt

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

--- ais/ai-00097.txt	1998/09/30 00:17:16	1.1
+++ ais/ai-00097.txt	1999/07/08 17:28:21	1.2
@@ -1,4 +1,4 @@
-!standard RM-4.6   (47)                               96-11-16  AI95-00097/05
+!standard RM-4.6   (47)                               99-07-08  AI95-00097/06
 !class confirmation 95-09-29
 !status WG9 approved 96-12-07
 !status ARG approved 10-0-2  96-10-07
@@ -9,13 +9,13 @@
 !difficulty Medium
 !subject Conversions between access types with different representations.
 
-!summary 96-07-23
+!summary
 
 If the Convention (other than Ada) of an access type has been specified
 by the user, then the semantics of type conversions involving that
 access type are implementation defined.
 
-!question 95-09-29
+!question
 
 It is possible to declare types that are normally convertible,
 but that have a pragma Convention that makes some such conversions
@@ -34,7 +34,7 @@
 What should happen when a value of C_Ptr has no corresponding value in
 Ada_Ptr?
 
-!response 95-09-29
+!response
 
 The semantics of such conversions are implementation defined.  This
 follows from the fact that pragma Convention is a representation pragma
@@ -49,8 +49,13 @@
 the other language, and doing so can make it impossible or impractical
 to obey the "normal" (non-interfaced) Ada semantics.
 
-!appendix 95-10-12
+!ACATS test
 
+No test is possible. This AI gives a permission for implementation-defined
+semantics, which of course cannot be tested in a portable way.
+
+!appendix
+
 !section RM-4.6(47)
 !subject Conversions between access types with different representations.
 !reference RM95-4.6(47-50)
@@ -135,14 +140,14 @@
 
 > It is possible to declare types such that the compiler will generate the
 > needed conversions between them.  For instance,
-> 
+>
 >       Type Ada_Ptr Is Access Integer; -- Integer is C-compatible in this
 >                                       -- implementation.
 >       Type C_Ptr Is New Ada_Ptr;
 >       Pragma Convention (C, C_Ptr);
-> 
+>
 > The value sets of such convertable types may not completely overlap.
-> 
+>
 > What should happen when a value of C_Ptr has no corresponding value in Ada_Ptr?
 
 It seems to me that this is implementation defined.  This follows from

Questions? Ask the ACAA Technical Agent