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

--- ai05s/ai05-0004-1.txt	2006/05/12 20:28:09	1.3
+++ ai05s/ai05-0004-1.txt	2006/11/10 06:44:49	1.4
@@ -1,4 +1,15 @@
-!standard C.7.1(17/2)                               06-05-12  AI05-0004-1/01
+!standard C.7.1(17/2)                               06-11-03  AI05-0004-1/02
+!standard 3.8(13.1/2)
+!standard 3.10.2(12.2/2)
+!standard 4.1(7)
+!standard 4.3.3(32)
+!standard 7.3(10.1/2)
+!standard 9.1(9.4/2)
+!standard 10.1.3(10)
+!standard 12.3(7)
+!standard A.11(4/2)
+!standard D.9(6)
+!standard J.1
 !class presentation 06-03-15
 !status work item 06-05-12
 !status received 06-03-15
@@ -13,10 +24,63 @@
 
 1) C.7.1(17/2) should say entry_body rather than entry body.
 
+2) 3.8(13.1/2) should say record_type_definition rather than record_type_declaration.
+
+3) 3.10.2(12.2/2) should say record_component_association rather than component_association.
+
+4) 4.3.3(32) should say parenthesized expression rather than parenthesized_expression.
+
+5) 4.1(7) should say attribute_references rather than attributes.
+
+6) 7.3(10.1/2) should say "defined by a derived_type_definition"
+rather than "is a derived_type_declaration".
+
+7) D.9(6) should say select_alternative rather than selective_accept_alternative.
+
+8) 12.3(7) should say (twice) generic_association rather than generic_parameter_assocation.
+
+9) 10.1.3(10) should say task declaration and protected declaration.
+
+10) A.11(4/2) should say Wide_Wide_Text_IO.Wide_Wide_Bounded_IO.
+
+11) The title of J.1 should be "Renamings of Library Units from Previous Versions
+of this Standard".
+
 !question
 
 1) Does C.7.1(17/2) apply to calls to Current_Task in an entry barrier? (Yes.)
 
+2) 3.8(13.1/2) talks about record_type_declaration. But there is no such thing;
+was record_type_definition meant instead? (Yes.)
+
+3) 3.10.2(12.2/2) talks about a component_association. But there is no such thing;
+was record_component_association meant instead? (Yes.)
+
+4) 4.3.3(32) talks about a parenthesized_expression. But there is no such thing;
+was parenthesized expression meant instead? (Yes.)
+
+5) 4.1(7) uses the syntax font for attributes, but the syntax for attributes is called
+a attribute_reference. Change this? (Yes.)
+
+6) 7.3(10.1/2) says "is a derived_type_definition", but there is no such thing.
+
+7) D.9(6) talks about a selective_accept_alternative. But there is no such thing;
+was select_alternative meant instead? (Yes.)
+
+8) 12.3(7) talks (twice) about a generic_parameter_association, but the syntax just
+a few lines above has no such thing. Is generic_association intended? (Yes.)
+
+9) 10.1.3(10) uses "task_declaration" and "protected_declaration", but these are
+not defined syntactically. Should "task declaration" and "protected declaration" be
+used instead? (Yes.)
+
+10) A.11(4/2) defines Wide_Wide_Text_IO.Wide_Bounded_IO, while A.11(5/2) defines
+Wide_Wide_Text_IO.Wide_Wide_Unbounded_IO. One of these names must be wrong.
+
+11) The title of J.1 says "Renamings of Ada 83 Library Units". This is the only
+occurrence of "Ada 83" in the Standard, and given that for ISO, that standard was
+Ada 87, this looks bad. This title should be changed.
+
 [Other questions here.]
 
 !recommendation
@@ -27,6 +91,27 @@
 
 1) C.7.1(17/2) should say entry_body rather than entry body.
 
+2) 3.8(13.1/2) should say record_type_definition rather than record_type_declaration.
+
+3) 3.10/2(12.2/2) should say record_component_association rather than component_association.
+
+4) 4.3.3(32) should say parenthesized expression rather than parenthesized_expression.
+
+5) 4.1(7) should say attribute_reference rather than attribute.
+
+6) 7.3(10.1/2) should say defined by a derived_type_definition.
+
+7) D.9(6) should say select_alternative.
+
+8) 12.3(7) should say generic_assocation.
+
+9) 10.1.3(10) should say task declaration and protected declaration.
+
+10) A.11(4/2) should say Wide_Wide_Text_IO.Wide_Wide_Bounded_IO.
+
+11) The title of J.1 should be "Renamings of Library Units from Previous Versions
+of this Standard".
+
 !discussion
 
 1) entry_barrier is syntactically within entry_body. C.7.1(17/2) however, says
@@ -35,6 +120,158 @@
 evaluated by any task. We therefore avoid confusion by changing the wording to use
 the syntax term.
 
+2) An obvious typo. [Editor's note: This correction was made in the Ada Europe RM edition;
+see below for why.]
+
+3) Record_component_association is the only thing that could have been meant; arrays
+don't have discriminants anyway. [Editor's note: This correction was made in the Ada
+Europe RM edition; see below for why.]
+
+4) There isn't a definition of the term "parenthisized expression", either, even though
+we use it all over the place. [Editor's note: This correction was made in the Ada
+Europe RM edition; see below for why.]
+
+5) This is talking about the syntax, which is defined directly about it. [Editor's note:
+This correction was made in the Ada Europe RM edition; see below for why.]
+
+6) Definitions define types, thus the new wording. [Editor's note:
+This correction was made in the Ada Europe RM edition; see below for why.]
+
+7) This is probably an old name for the syntax. [Editor's note:
+This correction was made in the Ada Europe RM edition; see below for why.]
+
+8) Oops. [Editor's note: This correction was made in the Ada Europe RM
+edition; see below for why.]
+
+9) This is probably an oversight. [Editor's note: This correction was made in the Ada Europe RM
+edition; see below for why.]
+
+10) This is an obvious error; Wide_Wide_Text_IO.Wide_Wide_Bounded_IO was obviously
+intended.
+
+11) "Ada 83" is meaningless from a standards perspective; it should not be used in
+normative text.
+
+Many of these corrections were made in the Ada Europe edition
+of the consolidated reference manual. The original versions were producing linking
+errors in the HTML versions (which link syntax terms to their definitions).
+But the error is present in the 'official' documents: the final version of the Ada 95 RM,
+Corrigendum, and Amendment; so we need to fix these 'officially'.
+
+!corrigendum 3.8(13.1/2)
+
+@drepl
+If a @fa<record_type_declaration> includes the reserved word @b<limited>, the
+type is called an @i<explicitly limited record> type.
+@dby
+If a @fa<record_type_definition> includes the reserved word @b<limited>, the
+type is called an @i<explicitly limited record> type.
+
+!corrigendum 3.10.2(12.2/2)
+
+@drepl
+@xinbull<If the value of the access discriminant is determined by a
+@fa<component_association> in an @fa<aggregate>, the accessibility
+level of the object or subprogram designated by the associated
+value (or library level if the value is null);>
+@dby
+@xinbull<If the value of the access discriminant is determined by a
+@fa<record_component_association> in an @fa<aggregate>, the accessibility
+level of the object or subprogram designated by the associated
+value (or library level if the value is null);>
+
+!corrigendum 4.1(7)
+
+@drepl
+Certain forms of name (@fa<indexed_component>s, @fa<selected_component>s,
+@fa<slice>s, and @fa<attribute>s) include a @fa<prefix> that is either itself
+a @fa<name> that denotes some related entity, or an @fa<implicit_dereference>
+of an access value that designates some related entity.
+@dby
+Certain forms of name (@fa<indexed_component>s, @fa<selected_component>s,
+@fa<slice>s, and @fa<attribute_reference>s) include a @fa<prefix> that is either
+itself a @fa<name> that denotes some related entity, or an @fa<implicit_dereference>
+of an access value that designates some related entity.
+
+!corrigendum 4.3.3(32)
+
+@drepl
+@s9<10  In an @fa<array_aggregate>, positional notation may only be used with two
+or more @fa<expression>s; a single @fa<expression> in parentheses is interpreted as a
+@fa<parenthesized_expression>. A @fa<named_array_aggregate>, such as (1 => X),
+may be used to specify an array with a single component.>
+@dby
+@s9<10  In an @fa<array_aggregate>, positional notation may only be used with two
+or more @fa<expression>s; a single @fa<expression> in parentheses is interpreted as a
+parenthesized expression. A @fa<named_array_aggregate>, such as (1 => X),
+may be used to specify an array with a single component.>
+
+!corrigendum 7.3.1(10.1/2)
+
+@drepl
+If the @fa<full_type_declaration> for a private extension is a
+@fa<derived_type_declaration>, then the reserved word @b<limited> shall appear
+in the @fa<full_type_declaration> if and only if it also appears in the
+@fa<private_extension_declaration>.
+@dby
+If the @fa<full_type_declaration> for a private extension is defined by a
+@fa<derived_type_definition>, then the reserved word @b<limited> shall appear
+in the @fa<full_type_declaration> if and only if it also appears in the
+@fa<private_extension_declaration>.
+
+!corrigendum 10.1.3(10)
+
+@drepl
+A @fa<package_body_stub> shall be the completion of a @fa<package_declaration>
+or @fa<generic_package_declaration>; a @fa<task_body_stub> shall be the
+completion of a @fa<task_declaration>; a @fa<protected_body_stub> shall
+be the completion of a @fa<protected_declaration>.
+@dby
+A @fa<package_body_stub> shall be the completion of a @fa<package_declaration>
+or @fa<generic_package_declaration>; a @fa<task_body_stub> shall be the
+completion of a task declaration; a @fa<protected_body_stub> shall
+be the completion of a protected declaration.
+
+!corrigendum 12.3(7)
+
+@drepl
+The @i<generic actual parameter> is either the @fa<explicit_generic_actual_parameter>
+given in a @fa<generic_parameter_association> for each formal, or the
+corresponding @fa<default_expression> or @fa<default_name> if no
+@fa<generic_parameter_association> is given for the formal. When the meaning
+is clear from context, the term “generic actual,” or simply “actual,” is used
+as a synonym for “generic actual parameter” and also for the view denoted by one,
+or the value of one. 
+@dby
+The @i<generic actual parameter> is either the @fa<explicit_generic_actual_parameter>
+given in a @fa<generic_association> for each formal, or the
+corresponding @fa<default_expression> or @fa<default_name> if no
+@fa<generic_association> is given for the formal. When the meaning
+is clear from context, the term “generic actual,” or simply “actual,” is used
+as a synonym for “generic actual parameter” and also for the view denoted by one,
+or the value of one. 
+
+!corrigendum A.11(4/2)
+
+@drepl
+The specification of package Wide_Text_IO.Wide_Bounded_IO is the same as that
+for Text_IO.Bounded_IO, except that any occurrence of Bounded_String is
+replaced by Wide_Bounded_String, and any occurrence of package Bounded is
+replaced by Wide_Bounded. The specification of package
+Wide_Wide_Text_IO.Wide_Bounded_IO is the same as that for
+Text_IO.Bounded_IO, except that any occurrence of Bounded_String is
+replaced by Wide_Wide_Bounded_String, and any occurrence of package Bounded
+is replaced by Wide_Wide_Bounded.
+@dby
+The specification of package Wide_Text_IO.Wide_Bounded_IO is the same as that
+for Text_IO.Bounded_IO, except that any occurrence of Bounded_String is
+replaced by Wide_Bounded_String, and any occurrence of package Bounded is
+replaced by Wide_Bounded. The specification of package
+Wide_Wide_Text_IO.Wide_Wide_Bounded_IO is the same as that for
+Text_IO.Bounded_IO, except that any occurrence of Bounded_String is
+replaced by Wide_Wide_Bounded_String, and any occurrence of package Bounded
+is replaced by Wide_Wide_Bounded.
+
 !corrigendum C.7.1(17/2)
 
 @drepl
@@ -46,6 +283,30 @@
 interrupt handler, or finalization of a task attribute. Program_Error is raised,
 or an implementation-defined value of the type Task_Id is returned. 
 
+!corrigendum D.9(6)
+
+@drepl
+When a @fa<delay_statement> appears in a @fa<delay_alternative> of a @fa<timed_entry_call>
+the selection of the entry call is attempted, regardless of the specified
+expiration time. When a @fa<delay_statement> appears in a @fa<selective_accept_alternative>,
+and a call is queued on one of the open entries, the selection of that
+entry call proceeds, regardless of the value of the delay expression.
+@dby
+When a @fa<delay_statement> appears in a @fa<delay_alternative> of a @fa<timed_entry_call>
+the selection of the entry call is attempted, regardless of the specified
+expiration time. When a @fa<delay_statement> appears in a @fa<select_alternative>,
+and a call is queued on one of the open entries, the selection of that
+entry call proceeds, regardless of the value of the delay expression.
+
+!corrigendum J.1(00)
+
+@drepl
+Renamings of Ada 83 Library Units
+@dby
+Renamings of Library Units from Previous Versions
+of this Standard
+
+
 !ACATS test
 
 None needed.
@@ -207,4 +468,5 @@
 useless.
 
 ****************************************************************
+