CVS difference for ai12s/ai12-0359-1.txt

Differences between 1.2 and version 1.3
Log of other versions for file ai12s/ai12-0359-1.txt

--- ai12s/ai12-0359-1.txt	2020/02/20 05:16:12	1.2
+++ ai12s/ai12-0359-1.txt	2020/03/15 07:59:45	1.3
@@ -1,7 +1,9 @@
-!standard E.1(5)                                       20-02-04  AI12-0359-1/01
+!standard E.1(5)                                       20-03-12  AI12-0359-1/02
 !standard E.2.1(11)
 !standard E.4(1)
 !class ramification 20-02-04
+!status Amendment 1-2012 20-03-11
+!status ARG Approved 14-0-0  20-03-11
 !status work item 20-02-04
 !status received 19-11-18
 !priority Low
@@ -55,10 +57,10 @@
 {AARM Ramification: A passive partition has no execution resources of its own,
 so while a call of a subprogram in a passive partition is a remote access to
 that subprogram, it is *not* a remote subprogram call (see E.4). The calling
-active partition executes the body of the subprogram in the passive partition.}
+active partition executes the body of the subprogram of the passive partition.}
 
 [Editor's note: Tucker suggested adding "active" into the wording above, but
-that would seem to leave accesses to passive partitions in limbo; accesses to]
+that would seem to leave accesses to passive partitions in limbo; accesses to
 the data in particular are certainly a form of remote access. I thought it
 better to differentiate between "remote access" and "remote subprogram call"
 (which is a subset of the former).]
@@ -124,6 +126,26 @@
 the data shared and persistent. In the DLL case, the code would live
 with the shared data. Calls are made to a DLL using the caller's stack;
 no marshalling is needed or expected.
+
+!corrigendum E.4(1)
+
+@drepl
+A @i<remote subprogram call> is a subprogram call that invokes the execution 
+of a subprogram in another partition. The partition that 
+originates the remote subprogram call is the @i<calling partition>, and the 
+partition that executes the corresponding subprogram body is the @i<called 
+partition>. Some remote procedure calls are allowed to return prior to the 
+completion of subprogram execution. These are called @i<asynchronous remote 
+procedure calls>.
+@dby
+A @i<remote subprogram call> is a subprogram call that invokes the execution 
+of a subprogram in another (active) partition. The partition that 
+originates the remote subprogram call is the @i<calling partition>, and the 
+partition that executes the corresponding subprogram body is the @i<called 
+partition>. Some remote procedure calls are allowed to return prior to the 
+completion of subprogram execution. These are called @i<asynchronous remote 
+procedure calls>.
+
 
 !ASIS
 

Questions? Ask the ACAA Technical Agent