CVS difference for ai12s/ai12-0152-1.txt
--- ai12s/ai12-0152-1.txt 2015/02/28 02:43:32 1.5
+++ ai12s/ai12-0152-1.txt 2015/03/03 22:37:54 1.6
@@ -1,4 +1,4 @@
-!standard 3.5.9(5) 15-02-26 AI05-0152-1/02
+!standard 3.5.9(5) 15-03-03 AI05-0152-1/03
!standard 3.5.9(18)
!standard 3.5.9(19)
!standard 11.3(2/2)
@@ -19,7 +19,7 @@
!priority Medium
!difficulty Easy
!qualifier Omission
-!subject Ambiguities in raise expression and derived type syntax
+!subject Eliminate ambiguities in raise expression and derived type syntax
!summary
Modify the Ada grammar to eliminate ambiguities.
@@ -416,7 +416,7 @@
implemented and in use in at least one compiler for several years. While
stand-alone raise expressions are unlikely in most contexts, some uses likely
exist and there doesn't seem to be any reason to break those. In particular,
-the construct "return raise TBD_Error;" (or some other convinient exception)
+the construct "return raise TBD_Error;" (or some other convenient exception)
is suggested for use when providing a body-to-be-defined later for a function.
This neatly gets around the requirement for "at least one return statement"
in a function body. It's also likely that some preconditions or postconditions
@@ -442,7 +442,7 @@
aspect specification during maintenance would trigger an annoying "parens
required". In both of these cases, it's unlikely that the programmer would
remember the parentheses requirement, and such a rule would increase Ada's
-reputation for obscure pickyness.
+reputation for obscure annoyances.
The wildest of these suggestions was to determine whether a "with" was part of
a preceding raise_expression or part of an aspect specification by determining
Questions? Ask the ACAA Technical Agent