CVS difference for ais/ai-00159.txt

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

--- ais/ai-00159.txt	1998/09/30 23:25:17	1.2
+++ ais/ai-00159.txt	1999/07/21 03:10:58	1.3
@@ -1,5 +1,6 @@
-!standard 09.10    (00)                               98-06-12  AI95-00159/04
+!standard 09.10    (00)                               99-07-20  AI95-00159/05
 !class binding interpretation 96-09-04
+!status Corrigendum 2000 99-07-20
 !status WG9 approved 98-06-12
 !status ARG Approved 11-0-1  98-04-01
 !status work item 96-09-08
@@ -8,7 +9,7 @@
 !difficulty Medium
 !subject Shared Variables in Shared_Passive?
 
-!summary 98-03-27
+!summary
 
 For the purposes of the Shared Variables rules in 9.10, with respect to
 shared variables in shared passive partitions, a synchronous remote
@@ -19,7 +20,7 @@
 but the body then proceeds in parallel, and thus does not signal the
 next action of the calling task.
 
-!question 98-04-01
+!question
 
 There is no task rendezvous between two partitions, and protected
 entries are disallowed in Shared_Passive packages, so how can two
@@ -27,15 +28,15 @@
 package performed on two different partitions be sequential as
 defined by RM95-9.10(11)?
 
-!recommendation 98-03-27
+!recommendation
 
 (See summary.)
 
-!wording 98-03-27
+!wording
 
 (See summary.)
 
-!discussion 98-03-27
+!discussion
 
 9.10 says:
 
@@ -106,7 +107,28 @@
 initialized, so long as they first do an RPC (that does not raise
 Communication_Error) to the initializing partition.
 
-!appendix 96-09-10
+!corrigendum E.04(20)
+
+@dinsa
+The implementation of remote subprogram calls shall conform to the PCS
+interface as defined by the specification of the language-defined package
+System.RPC (see E.5). The calling stub shall use the Do_RPC procedure unless
+the remote procedure call is asynchronous in which case Do_APC shall be used.
+On the receiving side, the corresponding receiving stub shall be invoked by
+the RPC-receiver.
+@dinst
+With respect to shared variables in shared passive library units, the
+corresponding subprogram body of synchronous remote procedure call is considered
+to be a part of the execution of the calling task while the corresponding
+subprogram body of an asynchronous remote procedure call, which proceeds in
+parallel with the calling task, does not signal the next action of the calling
+task (See 9.10).
+
+!ACATS test
+
+It is unknown (by the editor) if a C-Test can be created to check this rule.
+
+!appendix
 
 !section 9.10(00)
 !subject Shared Variables in Shared_Passive?

Questions? Ask the ACAA Technical Agent