CVS difference for ai05s/ai05-0171-1.txt

Differences between 1.5 and version 1.6
Log of other versions for file ai05s/ai05-0171-1.txt

--- ai05s/ai05-0171-1.txt	2010/08/13 01:02:19	1.5
+++ ai05s/ai05-0171-1.txt	2010/10/16 02:17:39	1.6
@@ -1,4 +1,4 @@
-!standard  D.13.1(4/2)                             10-08-12    AI05-0171-1/05
+!standard  D.13.1(4/2)                             10-10-15    AI05-0171-1/06
 !standard  D.16
 !class Amendment 09-10-22
 !status Amendment 2012 10-08-12
@@ -13,7 +13,7 @@
 
 The Ravenscar Profile, originally designed for single processors, has
 proven remarkably useful for modelling verifiable real-time
-single-processor systems. It can be extended to support
+single-processor systems. It is extended to support
 multiprocessor systems using a fully partitioned approach. The
 implementation of this scheme is simple, and it can be used to develop
 applications amenable to schedulability analysis.
@@ -62,7 +62,7 @@
 
       type CPU_Range is range 0 .. <implementation-defined>;
       Not_A_Specific_CPU : constant CPU_Range := 0;
-      subtype CPU is CPU_Range range 1 .. CPU_Range'last;
+      subtype CPU is CPU_Range range 1 .. CPU_Range'Last;
 
       function Number_Of_CPUs return CPU;
    end System.Multiprocessors;
@@ -97,9 +97,9 @@
 evaluated for each task object (see 9.1). The CPU value is then associated
 with the task object whose task_definition contains the pragma.
 
-Elaboration of a CPU pragma given immediately within the declarative_part of a
-subprogram_body has no effect; the CPU value is not associated with any
-task unless the pragma occurs within the main subprogram.
+A CPU pragma has no effect if it occurs immediately within the 
+declarative_part of a subprogram_body other than the main subprogram;
+the CPU value is not associated with any task.
 
 The CPU value is associated with the environment task if the pragma
 appears in the declarative_part of the main subprogram.
@@ -259,7 +259,7 @@
 
    @b<type> CPU_Range @b<is range> 0 .. @ft<@i<implementation-defined>>;
    Not_A_Specific_CPU : @b<constant> CPU_Range := 0;
-   @b<subtype> CPU @b<is> CPU_Range @b<range> 1 .. CPU_Range'last;
+   @b<subtype> CPU @b<is> CPU_Range @b<range> 1 .. CPU_Range'Last;
 
    @b<function> Number_Of_CPUs @b<return> CPU;
 @b<end> System.Multiprocessors;>
@@ -293,9 +293,9 @@
 evaluated for each task object (see 9.1). The CPU value is then associated
 with the task object whose @fa<task_definition> contains the pragma.
 
-Elaboration of a CPU pragma given immediately within the @fa<declarative_part> of a
-@fa<subprogram_body> has no effect; the CPU value is not associated with any
-task unless the pragma occurs within the main subprogram.
+A CPU pragma has no effect if it occurs immediately within the 
+@fa<declarative_part> of a @fa<subprogram_body> other than the main subprogram;
+the CPU value is not associated with any task.
 
 The CPU value is associated with the environment task if the pragma
 appears in the @fa<declarative_part> of the main subprogram.

Questions? Ask the ACAA Technical Agent