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

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

--- ai05s/ai05-0143-1.txt	2009/05/01 00:21:27	1.2
+++ ai05s/ai05-0143-1.txt	2009/07/11 03:06:22	1.3
@@ -1,6 +1,8 @@
-!standard 6.01 (18)                                 09-04-30  AI05-0143-1/02
+!standard 6.01 (18)                                 09-06-27  AI05-0143-1/03
 !standard 6.06 (03)
 !class Amendment 09-02-15
+!status Amendment 201Z 09-06-27
+!status ARG Approved  6-0-1  09-06-13
 !status work item 09-02-15
 !status received 09-02-15
 !priority High
@@ -62,12 +64,12 @@
 
 The last sentence of 6.1(18) is deleted.
 
-Add "of mode in" to 6.6(3):
-The subprogram_specification of a unary or binary operator shall have one or
-two parameters of mode in, respectively. A generic function instantiation whose
-designator is an operator_symbol is only allowed if the specification of the
-generic function has the corresponding number of parameters of mode in and no
-other parameters.
+Revise 6.6(3):
+The subprogram_specification of a unary or binary operator shall have one or two
+parameters, respectively. {The parameters shall be of mode in. }A generic function
+instantiation whose designator is an operator_symbol is only allowed if the
+specification of the generic function has the corresponding number of parameters{
+of mode in and no other parameters}.
 
 !discussion
 
@@ -97,7 +99,7 @@
 Thus, we add wording to restrict operator symbols to parameters of mode in.
 
 
-We considered using the presense of "in out" parameters on a function to
+We considered using the presence of "in out" parameters on a function to
 signal that the function needs read-write access to the protected object.
 This is a capability that is sorely missing from Ada, as the current rules
 force programmers to use procedures when they really want functions. As
@@ -162,6 +164,32 @@
 Conceptually, of course, the parameter to this function isn't even modified.
 We just need to use in out here to prevent someone from passing a constant,
 which could cause all manner of trouble.
+
+!corrigendum 6.1(18)
+
+@drepl
+The @i<parameter mode> of a formal parameter conveys the direction of information transfer
+with the actual parameter: @b<in>, @b<in out>, or @b<out>. Mode @b<in> is the default, and
+is the mode of a parameter defined by an @fa<access_definition>. The formal parameters of
+a function, if any, shall have the mode @b<in>. 
+@dby
+The @i<parameter mode> of a formal parameter conveys the direction of information transfer
+with the actual parameter: @b<in>, @b<in out>, or @b<out>. Mode @b<in> is the default, and
+is the mode of a parameter defined by an @fa<access_definition>. 
+
+!corrigendum 6.6(3)
+
+@drepl
+The @fa<subprogram_specification> of a unary or binary operator shall have one or two
+parameters, respectively. A generic function instantiation whose @fa<designator> is an
+@fa<operator_symbol> is only allowed if the specification of the generic function has
+the corresponding number of parameters.
+@dby
+The @fa<subprogram_specification> of a unary or binary operator shall have one or two
+parameters, respectively. The parameters shall be of mode @b<in>. A generic function
+instantiation whose @fa<designator> is an @fa<operator_symbol> is only allowed if the
+specification of the generic function has the corresponding number of parameters
+of mode @b<in> and no other parameters.
 
 !ACATS test
 

Questions? Ask the ACAA Technical Agent