CVS difference for ai12s/ai12-0164-1.txt

Differences between 1.5 and version 1.6
Log of other versions for file ai12s/ai12-0164-1.txt

--- ai12s/ai12-0164-1.txt	2015/11/24 03:26:50	1.5
+++ ai12s/ai12-0164-1.txt	2016/07/12 01:33:42	1.6
@@ -108,6 +108,9 @@
 It did not seem useful to have an attribute that can be used to query the aspect;
 use of such an attribute could lead to race conditions.
+These aspects would be very useful for restricted tasking profiles more general
+than Ravenscar. IRTAW has at least one such proposal for a new profile.
 ?? How are aspects handled??
@@ -217,4 +220,31 @@
 sure it is straightforward if you know what you are doing!!
+From: Steve Michell
+Sent: Saturday, June 11, 2016  9:33 AM
+My notes from IRTAW 2016 are appended.
+IRTAW 2016 discussed this item (April 2016) in the context of extensions to
+Ravenscar. The workshop was of the opinion that the only setting needed for
+entry size restrictions for Ravenscar is the one provided by pragma
+Restrictions(Max_Entry_Queue_Length=1). There was a proposal to the workshop
+to extend Ravenscar to permit more than a single entry in a protected
+type/object and to permit queue lengths longer than one, and settable
+Protected type by protected type. 
+Pat Rogers indicated that AdaCore would be creating a profile (nominally
+Extended-Ravenscar)  that  had those properties, but the workshop refused to
+agree to extending basic Ravenscar in this way. The workshop also stated its
+preference that the new profile not be called Ravenscar-something. It should
+be noted that pragma restrictions(Max_Entry_Queue_Length=N) is a library-level
+item that affects all entries in a program, so being able to apply this
+restriction on a type-by-type is important.  
+For a new profile that limits entry queue lengths, either by task type or by
+protected type, this aspect would be very useful, and since AdaCore is
+finishing the implementation of extended-Ravenscar, may be essential.

Questions? Ask the ACAA Technical Agent