CVS difference for ais/ai-00382.txt

Differences between 1.4 and version 1.5
Log of other versions for file ais/ai-00382.txt

--- ais/ai-00382.txt	2004/12/09 19:55:37	1.4
+++ ais/ai-00382.txt	2005/06/16 23:47:37	1.5
@@ -1,4 +1,6 @@
-!standard 8.6(17)                                    04-12-01  AI95-00382/03
+!standard 8.6(17)                                    05-06-05  AI95-00382/04
+!standard 9.1(19)
+!standard 9.4(21)
 !class amendment 04-08-27
 !status Amendment 200Y 04-12-01
 !status ARG Approved 8-0-2  04-11-19
@@ -80,6 +82,20 @@
 "access T'Class" appearing within the declarative region of T: here T denotes
 the type, not the current instance.
 
+Replace 9.1(19) by:
+
+2  Within the declaration or body of a task unit other than in an
+access_definition, the name of the task unit denotes the current instance of
+the unit (see 8.6), rather than the first subtype of the corresponding task
+type (and thus the name cannot be used as a subtype_mark).
+
+Replace 9.4(21) by:
+
+13  Within the declaration or body of a protected unit other than in an
+access_definition, the name of the protected unit denotes the current instance
+of the unit (see 8.6), rather than the first subtype of the corresponding
+protected type (and thus the name cannot be used as a subtype_mark).
+
 !discussion
 
 (See proposal.)
@@ -112,6 +128,34 @@
 appears within the @fa<subtype_mark> of an @fa<access_definition> for an
 access-to-object type, or within the subtype of a parameter or result of an
 access-to-subprogram type.
+
+!corrigendum 9.1(19)
+
+@drepl
+@xindent<@s9<2  Within the declaration or body of a task unit, the name of the
+task unit denotes the current instance of
+the unit (see 8.6), rather than the first subtype of the corresponding task
+type (and thus the name cannot be used as a @fa<subtype_mark>).>>
+@dby
+@xindent<@s9<2  Within the declaration or body of a task unit other than in an
+@fa<access_definition>, the name of the task unit denotes the current instance
+of the unit (see 8.6), rather than the first subtype of the corresponding task
+type (and thus the name cannot be used as a @fa<subtype_mark>).>>
+
+!corrigendum 9.4(21)
+
+@drepl
+@xindent<@s9<13  Within the declaration or body of a protected unit, the name
+of the protected unit denotes the current instance of the unit (see 8.6),
+rather than the first subtype of the corresponding protected type (and thus the
+name cannot be used as a @fa<subtype_mark>).>>
+@dby
+@xindent<@s9<13  Within the declaration or body of a protected unit other than
+in an @fa<access_definition>, the name of the protected unit denotes the
+current instance of the unit (see 8.6), rather than the first subtype of the
+corresponding protected type (and thus the name cannot be used as a
+@fa<subtype_mark>).>>
+
 
 !ACATS test
 

Questions? Ask the ACAA Technical Agent