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

Differences between 1.3 and version 1.4
Log of other versions for file ai05s/ai05-0225-1.txt

--- ai05s/ai05-0225-1.txt	2011/01/27 06:06:17	1.3
+++ ai05s/ai05-0225-1.txt	2011/03/11 02:10:31	1.4
@@ -1,4 +1,4 @@
-!standard  9.5(7.1/2)                                11-01-25    AI05-0225-1/03
+!standard  9.5(7.1/2)                                11-02-19    AI05-0225-1/04
 !class binding interpretation 10-10-21
 !status work item 10-10-21
 !status received 10-06-04
@@ -48,6 +48,25 @@
 
 !wording
 
+Replace 9.5(2):
+
+Any call on an entry or on a protected subprogram identifies a *target object*
+for the operation, which is either a task (for an entry call) or a protected
+object (for an entry call or a protected subprogram call). The target object is
+considered an implicit parameter to the operation, and is determined by the
+operation name (or prefix) used in the call on the operation, as follows:
+
+with:
+
+Any name that denotes an entry or a protected subprogram identifies a
+*target object*, which is either a task (for an entry) or a protected
+object (for an entry or a protected subprogram). The target object
+identified by the operation name (or prefix) used in a call on an entry
+or a protected subprogram is considered an implicit parameter to the
+call. The target object is determined as follows:
+
+
+
 Replace 9.5(7.1/2):
 
 The view of the target protected object associated with a call of a protected
@@ -55,11 +74,10 @@
 
 with:
 
-The name of a protected procedure or entry of a constant view of a protected
-object is illegal in the following cases: the name of a call, the prefix of an
-Access attribute, the name of a subprogram_renaming_declaration, an
-explicit_generic_actual_parameter, or the subprogram_default of a
-formal_subprogram_declaration.
+For a name that denotes a protected procedure, the view of the target object
+shall be a variable. For a name that denotes an entry, the view of the target
+object shall be a variable unless the name is the prefix of a reference to the
+Count attribute.
 
 AARM Note: The point is to prevent any calls to such a name, directly, or via an
 access value, renames, or generic formal subprogram. It is, however, legal to
@@ -83,6 +101,10 @@
 
 An ACATS B-Test needs to be constructed to test examples like the one in the
 question (and others implied by the new rule).
+
+!ASIS
+
+No impact on ASIS.
 
 !appendix
 

Questions? Ask the ACAA Technical Agent