CVS difference for ais/ai-00159.txt

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

--- ais/ai-00159.txt	2000/06/20 04:22:43	1.7
+++ ais/ai-00159.txt	2000/07/13 04:31:29	1.8
@@ -9,11 +9,11 @@
 !priority Medium
 !difficulty Medium
 !qualifier Clarification
-!subject Shared Variables in Shared_Passive?
+!subject Shared variables in Shared_Passive?
 
 !summary
 
-For the purposes of the Shared Variables rules in 9.10, with respect to
+For the purposes of the shared variables rules in 9.10, with respect to
 shared variables in shared passive partitions, a synchronous remote
 procedure call is considered to be part of the execution of the calling
 task.
@@ -42,7 +42,7 @@
 
 9.10 says:
 
-  2   Separate tasks normally proceed independently and concurrently with one
+  (2)  Separate tasks normally proceed independently and concurrently with one
   another.  However, task interactions can be used to synchronize the actions
   of two or more tasks to allow, for example, meaningful communication by the
   direct updating and reading of variables shared between the tasks.  The
@@ -50,41 +50,41 @@
   of one task signals an action of the other task; an action A1 is defined to
   signal an action A2 under the following circumstances:
 
-    3  If A1 and A2 are part of the execution of the same task, and the
-       language rules require A1 to be performed before A2;
+    (3) If A1 and A2 are part of the execution of the same task, and the
+        language rules require A1 to be performed before A2;
 
     ...
 
-    7  If A1 is the action of issuing an entry call, and A2 is part of
-       the corresponding execution of the appropriate entry_body or
-       accept_statement.
-
-    8  If A1 is part of the execution of an accept_statement or entry_
-       body, and A2 is the action of returning from the corresponding
-       entry call;
-
-    9  If A1 is part of the execution of a protected procedure body or
-       entry_body for a given protected object, and A2 is part of a
-       later execution of an entry_body for the same protected object;
+    (7) If A1 is the action of issuing an entry call, and A2 is part of
+        the corresponding execution of the appropriate entry_body or
+        accept_statement.
+
+    (8) If A1 is part of the execution of an accept_statement or entry_
+        body, and A2 is the action of returning from the corresponding
+        entry call;
+
+    (9) If A1 is part of the execution of a protected procedure body or
+        entry_body for a given protected object, and A2 is part of a
+        later execution of an entry_body for the same protected object;
 
-    10  If A1 signals some action that in turn signals A2.
+    (10)If A1 signals some action that in turn signals A2.
 
 
   Erroneous Execution
 
-  11   Given an action of assigning to an object, and an action of reading or
+  (11) Given an action of assigning to an object, and an action of reading or
   updating a part of the same object (or of a neighboring object if the two are
   not independently addressable), then the execution of the actions is
   erroneous unless the actions are sequential.  Two actions are sequential if
   one of the following is true:
 
-    12  One action signals the other;
+    (12) One action signals the other;
 
-    13  Both actions occur as part of the execution of the same task;
+    (13) Both actions occur as part of the execution of the same task;
 
-    14  Both actions occur as part of protected actions on the same
-        protected object, and at most one of the actions is part of a
-        call on a protected function of the protected object.
+    (14) Both actions occur as part of protected actions on the same
+         protected object, and at most one of the actions is part of a
+         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 signaling, so long as we view the call as taking place within

Questions? Ask the ACAA Technical Agent