CVS difference for ai12s/ai12-0109-1.txt

Differences between 1.3 and version 1.4
Log of other versions for file ai12s/ai12-0109-1.txt

--- ai12s/ai12-0109-1.txt	2014/11/18 06:52:29	1.3
+++ ai12s/ai12-0109-1.txt	2015/01/20 22:39:13	1.4
@@ -1,4 +1,4 @@
-!standard 13.1(10/3)                                14-11-14  AI05-0109-1/02
+!standard 13.1(10/3)                                15-01-20  AI05-0109-1/03
 !class binding interpretation 14-05-15
 !status Corrigendum 2015 14-11-14
 !status ARG Approved 7-0-1  14-10-19
@@ -94,11 +94,13 @@
+Considering the questions separately:
 The rule 13.1(10/3) is a strange combination of a required semantic rule
 and a methodological restriction. It is intended to prevent the need to
-make implicit conversions when calling n inherited primitive subprogram.
+make implicit conversions when calling an inherited primitive subprogram.
 In some cases (such as limited by-reference types), making a copy of an
 object is prohibited and therefore it is impossible to make any implicit
@@ -118,7 +120,7 @@
 implicit conversions (but also preventing inexpensive implicit conversions).
 Methodological restrictions are always questionable, as they merely prevent a
-programmer from doing something that they may actually want to do. After all,
+programmer from doing something that they may actually need to do. After all,
 there are plenty of operations that can be quite expensive in practice
 (controlled types, equality of composites, and so on). Generally, it's better
 to let knowledgable users write the code that they need (especially given that
@@ -131,7 +133,7 @@
 order to use Ada-language conversions. That means that the standard
 organization of putting a type and its operations together in a package cannot
 be followed - the operations have to placed somewhere else in order to take
-advantage of compile-generated representation change. For many types
+advantage of compiler-generated representation change. For many types
 (especially ones in packages already in use for which moving operations would
 require changes to many clients), the net effect is that derivation is
 infeasible and the representation changes end up getting written manually by
@@ -146,8 +148,7 @@
 As such, we only fix as much of the loophole as necessary to eliminate semantic
 problems. We extend the rules from AI05-0246-1 so that they cover such late
-representation changes, as well as banning them for Small. This is the minimum
-that we can do.
+representation changes. This is the minimum that we have to do.
 It would be appealing to relax 13.1(10/3) to match the new rule. After all,
 this provides a way to end-run 13.1(10/3), much like generics provided a

Questions? Ask the ACAA Technical Agent