CVS difference for ais/ai-00159.txt
--- ais/ai-00159.txt 1999/08/31 22:53:55 1.4
+++ ais/ai-00159.txt 2000/04/14 01:45:08 1.5
@@ -1,4 +1,4 @@
-!standard 09.10 (00) 99-08-31 AI95-00159/05
+!standard 09.10 (00) 00-04-11 AI95-00159/06
!standard E.04 (20)
!class binding interpretation 96-09-04
!status Corrigendum 2000 99-07-20
@@ -85,7 +85,7 @@
call on a protected function of the protected object.
A remote procedure call is a procedure call, so 9.10(3) implies that
-RPC's are signalling, so long as we view the call as taking place within
+RPC's are signaling, so long as we view the call as taking place within
the execution of a single task.
The only problem is that asynchronous RPC's are weird; the caller
@@ -120,11 +120,11 @@
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).
+execution of the corresponding subprogram body of a synchronous remote
+procedure call is considered to be part of the execution of the calling task.
+The execution of the corresponding subprogram body of an asynchronous remote
+procedure call, proceeds in parallel with the calling task, and does not signal
+the next action of the calling task (see 9.10).
Questions? Ask the ACAA Technical Agent