CVS difference for ais/ai-00265.txt

Differences between 1.5 and version 1.6
Log of other versions for file ais/ai-00265.txt

--- ais/ai-00265.txt	2003/02/19 00:31:10	1.5
+++ ais/ai-00265.txt	2003/02/19 00:50:44	1.6
@@ -1,4 +1,4 @@
-!standard D.2.2 (5)                                03-02-08  AI95-00265/05
+!standard D.2.2 (5)                                03-02-09  AI95-00265/06
 !standard D.7 (00)
 !class amendment 01-05-10
 !status work item 01-05-10
@@ -52,44 +52,47 @@
 
 Syntax
 The form of a pragma Partition_Elaboration_Policy is as follows:
-pragma Partition_Elaboration_Policy ( <Policy_Identifier> );
+pragma Partition_Elaboration_Policy ( <policy_identifier> );
 
-The Policy_Identifier shall be either Sequential, Concurrent or an
-implementation-defined identifier; Concurrent is the default.
+The policy_identifier shall be either Sequential, Concurrent or an
+implementation-defined identifier.
 
-Legality Rules
+Post-Compilation Rules
 If the Sequential policy is specified for a
 partition then pragma Restrictions (No_Task_Hierarchy) shall
 also be specified for the partition.
 
-Post-Compilation Rules
 The pragma is a configuration pragma. It applies to all compilation
 units in a partition.
 
 Dynamic Semantics
 
-If the Policy_Identifier is Sequential, all task activation for library-level
+Notwithstanding what this International Standard says elsewhere, this
+pragma allows partition elaboration rules concerning task activation
+and interrupt attachment to be changed. If the policy_identifier
+is Concurrent, or if there is no pragma Partition_Elaboration_Policy
+defined for the partition, then the rules defined elsewhere in this
+Standard apply.
+
+If the policy_identifier is Sequential, all task activation for library-level
 tasks, and all interrupt handler attachment for library-level interrupt
 handlers is deferred. The deferred task activation and handler attachment
 occurs after the elaboration of all library_items prior to calling the main
 subprogram. At this point the Environment task is suspended until all deferred
 task activation and handler attachment is complete.
 
-If any deferred task activation fails then Tasking_Error is raised
+If any deferred task activation fails, then Tasking_Error is raised
 in the Environment task. The Environment task and all tasks whose
 activations fail are terminated. If a number of dynamic interrupt
-handler attachments for the same interrupt are defered then the
-handler most recently deferred is attached.
-
-If the Policy_Identifier is Concurrent the execution of
-the declarative part of the Environment task is as defined in 10.2.
+handler attachments for the same interrupt are deferred then the
+most recently call of Attach_Handler or Exchange_Handler determines
+which handler is attached.
 
 Implementation Advice
 
 If the Policy_Identifier is Sequential and the Environment task
 becomes permanently blocked then the partition is deadlocked
-and it is recommended that the active partition be immediately
-terminated.
+and it is recommended that it be immediately terminated.
 
 Implementation Permission
 

Questions? Ask the ACAA Technical Agent