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

Differences between 1.10 and version 1.11
Log of other versions for file ai12s/ai12-0127-1.txt

--- ai12s/ai12-0127-1.txt	2016/10/06 04:09:17	1.10
+++ ai12s/ai12-0127-1.txt	2017/09/06 03:28:43	1.11
@@ -1718,3 +1718,126 @@
 
 ****************************************************************
 
+From: Stephen Leake
+Sent: Saturday, August 5, 2017  12:15 PM
+
+!topic typos in ai12-0127
+!reference Ada 202x RM4.3.4
+!from Stephen Leake 2017-08-05
+!keywords delta aggregates
+!discussion
+
+I just read ai12-0127 (at
+http://www.ada-auth.org/cgi-bin/cvsweb.cgi/ai12s/ai12-0127-1.txt?rev=1.10)
+(with an eye towards enhancing Emacs Ada mode to support the new syntax), and
+I noticed a few typos:
+
+
+4.3.4
+    For an array_delta_aggregates, the expected type for each
+    discrete_choice in an array_component_association is the index type of
+    type of the delta aggregate.
+
+       "array_delta_aggregates" should not be plural
+
+Examples:
+
+    New_Cell : Cell := Min_Cell (Link) with delta Value => 42);
+
+        missing left paren before Min_Cell
+
+    A1 : Vector := ((1, 2, 3) with delta Integer (Random * 3.0) => 14.2);
+
+        components in base expression must be real; (1.0, 2.0, 3.0)
+
+****************************************************************
+
+From: Christoph Grein
+Sent: Wednesday, August 9, 2017  9:30 AM
+
+The record Rec of this example seems to have among others the two components
+Color and Shape. Thus the Post condition seems to return False:
+
+    procedure Foo (Fighters : in out Rec)
+       with Post => (Fighters.Colour = Black and
+                     Fighters = (Fighters'Old with delta Shape => Trapazoid));
+
+Shouldn't this be
+
+    procedure Foo (Fighters : in out Rec)
+       with Post => (Fighters = (Fighters'Old with delta
+                                   Shape  => Trapazoid,
+                                   Colour => Black));
+
+(This example is not part of the examples of the wording section, so the error
+is not overly fatal, because it won't go into the RM.)
+
+****************************************************************
+
+From: Simon Wright
+Sent: Wednesday, August 9, 2017  10:26 AM
+
+> The record Rec of this example seems to have among others the two 
+> components Color and Shape. Thus the Post condition seems to return False:
+> 
+>   procedure Foo (Fighters : in out Rec)
+>      with Post => (Fighters.Colour = Black and
+>                    Fighters = (Fighters'Old with delta Shape => 
+> Trapazoid));
+
+Spello: TrapEzoid
+
+****************************************************************
+
+From: Gary Dismukes
+Sent: Wednesday, August 9, 2017  11:56 AM
+
+> Shouldn't this be
+> 
+>    procedure Foo (Fighters : in out Rec)
+>       with Post => (Fighters = (Fighters'Old with delta
+>                                   Shape  => Trapazoid,
+>                                   Colour => Black));
+> 
+> (This example is not part of the examples of the wording section, so 
+> the error is not overly fatal, because it won't go into the RM.)
+
+Sounds right to me.
+
+Maybe the spelling should also be fixed: "Trapazoid" should be "Trapezoid". :-)
+
+****************************************************************
+
+From: Randy Brukardt
+Sent: Wednesday, August 9, 2017  10:39 PM
+
+> I just read ai12-0127 (at
+> http://www.ada-auth.org/cgi-bin/cvsweb.cgi/ai12s/ai12-0127-1.t
+> xt?rev=1.10)
+> (with an eye towards enhancing Emacs Ada mode to support the new 
+> syntax), and I noticed a few typos:
+...
+
+Thanks, I think. Since this is an open AI, it hasn't yet undergone a
+comprehensive editorial review, and it is not unusual for it to contain a
+bunch of typos. In this particular case, the AI is awaiting an update and a
+number of problems (including typos) are supposed to be fixed by the author.
+At least part of the text is likely to change substantially.
+
+In any case, the editor (that would be me) is not in a position to make
+changes to this AI or most other AIs (other than the ones assigned to me)
+as there is a race condition between me and the actual author. Experience
+shows that attempts to fix things often disappear in the next draft anyway
+(when the author starts from some other version of the AI). I'll file this
+mail into the AI, where it might very well be forgotten (or even disappear as
+a victim of a race condition).
+
+As such, it's not very valuable to make editorial comments on open AIs outside
+of ARG meetings (or even in ARG meetings, as a significant number of AIs are
+redrafted without fixing them). They're best left until the AI becomes
+ARG-approved and is in its editorial review period. Either that or contact the
+AI author (you can find who that is in the most recent version of the ARG
+meeting minutes - if it's not assigned to anyone, it's in near-death limbo and
+not worth worrying about).
+
+****************************************************************

Questions? Ask the ACAA Technical Agent