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

Differences between 1.12 and version 1.13
Log of other versions for file ai05s/ai05-0013-1.txt

--- ai05s/ai05-0013-1.txt	2008/03/07 06:15:18	1.12
+++ ai05s/ai05-0013-1.txt	2008/05/10 05:14:33	1.13
@@ -1,4 +1,4 @@
-!standard 7.6(9.4/2)                                 08-02-21    AI05-0013-1/11
+!standard 7.6(9.4/2)                                 08-04-09    AI05-0013-1/12
 !standard 13.12(8)
 !standard D.7(3)
 !standard D.7(4/2)
@@ -63,7 +63,7 @@
 
 it is a class-wide type; or
 
-In 13.2(8), replace
+In 13.12(8), replace
     A pragma Restrictions is a configuration pragma; unless otherwise
     specified for a particular restriction, a partition shall obey the
     restriction if a pragma Restrictions applies to any compilation unit
@@ -82,10 +82,10 @@
           of the program, as indicated by the specification of runtime
           behavior associated with a violation of the requirement.
 
-          AARM Ramification: In this case, there is no post-compilation check
-              required.
+          AARM Ramification: In this latter case, there is no post-compilation
+              check required.
    
-Replace D.7(3/2) with:
+Replace D.7(3) with:
    No task depends on a task other than the environment task of
    the partition.
 
@@ -106,7 +106,7 @@
 Modify D.7(10/2) as follows:
 
 No_Dynamic_Attachment
-   There is no {use of}[call to] to any of the operations defined in package
+   There is no {use of}[call to] any of the operations defined in package
    Interrupts (Is_Reserved, Is_Attached, Current_Handler, Attach_Handler,
    Exchange_Handler, Detach_Handler, and Reference).
 
@@ -182,15 +182,12 @@
 a task or an object with a task part or coextension. That's because the
 task is initially created on the master of the return statement (before
 being moved to master of the call site), and that master violates the
-restriction.
+restriction. We have concluded that this behavior for the restriction is
+acceptable, as returning tasks in this way is complex, and this restriction is part
+of the Ravenscar profile. Moreover, having subtly different semantics for
+Ravenscar programs does not seem desirable.
 
-We have concluded that this behavior for the restriction is acceptable,
-as returning tasks in this way is complex, and this restriction is part
-of the Ravenscar profile. Moreover, eliminating the master hand-off for
-Ravenscar would make the semantics subtly different for Ravenscar programs.
-That does not seem desirable.
 
-
 !corrigendum 7.6(9.4/2)
 
 @drepl
@@ -219,7 +216,7 @@
 of the program, as indicated by the specification of runtime
 behavior associated with a violation of the requirement.>
 
-!corrigendum D.7(3/2)
+!corrigendum D.7(3)
 
 @drepl
 @xindent<All (nonenvironment) tasks depend directly on the environment task
@@ -236,18 +233,18 @@
 @dby
 @xindent<Objects of a type that needs finalization (see 7.6) are declared
 only at library level. If an access type does not have library-level
-accessibility, then there are no @fa<allocator>s where the type
-determined by the @fa<subtype_mark> of the @fa<subtype_indication> or
+accessibility, then there are no @fa<allocator>s of the type where the
+type determined by the @fa<subtype_mark> of the @fa<subtype_indication> or
 @fa<qualified_expression> needs finalization.>
 
 !corrigendum D.7(10/2)
 
 @drepl
-@xindent<There is no call to to any of the operations defined in package
+@xindent<There is no call to any of the operations defined in package
 Interrupts (Is_Reserved, Is_Attached, Current_Handler, Attach_Handler,
 Exchange_Handler, Detach_Handler, and Reference).>
 @dby
-@xindent<There is no use of to any of the operations defined in package
+@xindent<There is no use of any of the operations defined in package
 Interrupts (Is_Reserved, Is_Attached, Current_Handler, Attach_Handler,
 Exchange_Handler, Detach_Handler, and Reference).>
 

Questions? Ask the ACAA Technical Agent