CVS difference for ai12s/ai12-0164-1.txt
--- ai12s/ai12-0164-1.txt 2015/06/18 05:56:10 1.1
+++ ai12s/ai12-0164-1.txt 2015/10/09 00:12:24 1.2
@@ -1,4 +1,4 @@
-!standard 5.5.2(2/3) 15-06-04 AI05-0164-1/00
+!standard 5.5.2(2/3) 15-09-14 AI05-0164-1/01
!class Amendment 15-06-04
@@ -6,7 +6,7 @@
!status received 15-04-24
-!subject Max Queue Length aspect for protected entries
+!subject Max Queue Length aspect for entries
@@ -14,18 +14,19 @@
In order to facilitate timing analysis, a new representation aspect
-Max_Queue_Length is needed.
+Max_Entry_Queue_Length is needed. This should be applicable to a specific
+entry or a type (task or protected).
-Max_Queue_Length for a protected entry declaration that specifies the maximum
+Max_Entry_Queue_Length for a entry declaration specifies the maximum
number of callers allowed on that entry. Violation of this restriction results
-in the raising of Program_Error at the point of the call or requeue. A check is
-made that the expression specified in the Max_Queue_Length aspect lower or equal
-than the Max_Entry_Queue_Length partition-wide restriction. If the check fails,
-Program_Error is raised.
+in the raising of Program_Error at the point of the call or requeue.
+A check is made that the expression specified in the Max_Entry_Queue_Length
+aspect for an entry is no higher than any specified for the corresponding type,
+and both are no higher than the Max_Entry_Queue_Length partition-wide
+restriction. If either check fails, Program_Error is raised.
@@ -41,6 +42,14 @@
If a limit for an individual entry is needed, that seems more appropriate for a
precondition or assertion.
+Aspect should apply to all entries not just protected ones.
+Seems only reasonable to have an aspect for a specific entry or for the object's
+type. Aspects should only be able to tighten any more global restriction.
+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.
Questions? Ask the ACAA Technical Agent