CVS difference for ais/ai-00298.txt

Differences between 1.11 and version 1.12
Log of other versions for file ais/ai-00298.txt

--- ais/ai-00298.txt	2005/04/13 05:37:10	1.11
+++ ais/ai-00298.txt	2005/12/15 02:44:03	1.12
@@ -1,4 +1,4 @@
-!standard D.2.4 (00)                                   04-05-24  AI95-00298/05
+!standard D.2.4 (00)                                   05-12-05  AI95-00298/06
 !reference AI95-00321
 !class amendment 02-06-01
 !status Amendment 200Y 03-07-02
@@ -76,15 +76,18 @@
 
 o When a task executes a delay_statement that does not result in
 blocking, it is added to the tail of the ready queue for its active
-priority. This is a task dispatching point (see D.2.1).
+priority.
 
+For this policy, a non-blocking delay_statement is the only non-blocking event
+that is a task dispatching point (see D.2.1).
+
 Implementation Permission
 
 Since implementations are allowed to round all ceiling priorities in
 subrange System.Priority to System.Priority'Last (see D.3), an
 implementation may allow a task to execute within a protected object
-without raising its active priority provided the protected object does
-not contain pragma Interrupt_Priority, Interrupt_Handler or Attach_Handler.
+without raising its active priority provided the associated protected unit
+does not contain pragma Interrupt_Priority, Interrupt_Handler or Attach_Handler.
 
 !discussion
 
@@ -205,14 +208,17 @@
 
 @xbullet<When a task executes a @fa<delay_statement> that does not result in
 blocking, it is added to the tail of the ready queue for its active
-priority. This is a task dispatching point (see D.2.1).>
+priority.>
+
+For this policy, a non-blocking delay_statement is the only @fa<non-blocking>
+event that is a task dispatching point (see D.2.1).
 
 @i<@s8<Implementation Permissions>>
 
 Since implementations are allowed to round all ceiling priorities in
 subrange System.Priority to System.Priority'Last (see D.3), an
 implementation may allow a task to execute within a protected object
-without raising its active priority provided the protected object does
+without raising its active priority provided the associated protected unit does
 not contain pragma Interrupt_Priority, Interrupt_Handler or Attach_Handler.
 
 !ACATS Test

Questions? Ask the ACAA Technical Agent