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

Differences between 1.5 and version 1.6
Log of other versions for file ai12s/ai12-0034-1.txt

--- ai12s/ai12-0034-1.txt	2013/07/18 01:56:24	1.5
+++ ai12s/ai12-0034-1.txt	2013/10/07 23:56:41	1.6
@@ -1,4 +1,4 @@
-!standard E.4(8)                               13-07-17    AI12-0034-1/04
+!standard E.4(8)                               13-10-07    AI12-0034-1/05
 !class binding interpretation 12-06-06
 !status Amendment 202x 13-07-17
 !status ARG Approved 9-0-0  13-06-16
@@ -9,7 +9,7 @@
 !subject Remote stream attribute calls
 !summary
 
-Dereferencing a remote-access-to-classwide type to make a dispatching call to a
+Dereferencing a remote access-to-classwide type to make a dispatching call to a
 stream attribute is not allowed.
 
 !question
@@ -109,13 +109,13 @@
 no RCI packages in this partition (and no other partitions). That means that
 marshalling and unmarshalling and PCS use is required, even though the call has
 to be ultimately local. Even in programs that have multiple partitions, types
-declared in Pure and Remote_Types packages will be replicated into each
+declared in Pure and Remote_Types packages will be replicated in each
 partition, meaning that the associated calls on primitives are going to be
 local.
 
 Moreover, it is necessary to dispatch in order to do marshalling (that's the
 only way to know how to marshall the specific type of the designated object),
-and it silly to dispatch multiple times when once would do. Thus, it's likely
+and it is silly to dispatch multiple times when once would do. Thus, it's likely
 that the implementation will marshall in stubs that are dispatched to, one for
 each specific type; with that implementation there is no need for remote calls
 (specifically marshalling and unmarshalling) if the specific subprogram is

Questions? Ask the ACAA Technical Agent