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

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

--- ai05s/ai05-0259-1.txt	2011/06/20 04:55:19	1.2
+++ ai05s/ai05-0259-1.txt	2011/07/29 03:26:56	1.3
@@ -1,45 +1,36 @@
-!standard  3.10(11)                               11-06-19    AI05-0259-1/01
-!class binding interpretation 11-06-19
+!standard  6.3.1(13.1/2)                              11-07-28    AI05-0259-1/02
+!class confirmation 11-07-28
+!status ARG Approved 12-0-0  11-06-25
 !status work item 11-06-16
 !status received 11-05-31
 !priority Low
 !difficulty Easy
 !qualifier Omission
-!subject Default convention of anonymous access-subprogram parameters
+!subject Default convention of anonymous access-to-subprogram parameters
-** TBD.
+6.3.1(13.1/2) provides the convention for anonymous access-to-subprogram
 What is the convention of anonymous access-to-subprogram types in
 a subprogram that has another convention (like C)?
-** TBD
+6.3.1(13.1/2) says: "The calling convention for an anonymous access-to-subprogram
+parameter or anonymous access-to-subprogram result is protected if the reserved
+word protected appears in its definition and otherwise is the convention of the
+subprogram that contains the parameter."
-Editor's one minute take:
-Requiring the convention to be Ada would seem to cause problems for
-Import/Export. C is unlikely to be happy with an Ada closure.
-OTOH, implementing the semantics of the access (for Convention/Export)
-would be a problem. How could one get a closure from C??
-Thus the answer is not obvious here -- probably we need a combination of
-conventions and "recommended level of support".
 !ACATS Test
-** TBD.
+No need for a separate ACATS test.
-** TBD.
+No ASIS impact.

Questions? Ask the ACAA Technical Agent