CVS difference for ai22s/ai22-0065-1.html

Differences between 1.4 and version 1.5
Log of other versions for file ai22s/ai22-0065-1.html

--- ai22s/ai22-0065-1.html	2023/07/12 01:01:04	1.4
+++ ai22s/ai22-0065-1.html	2023/09/08 00:32:34	1.5
@@ -1,4 +1,4 @@
-<html><head><meta content="text/html; charset=UTF-8" http-equiv="content-type"><title>AI22-0065-1/02</title>
+<html><head><meta content="text/html; charset=UTF-8" http-equiv="content-type"><title>AI22-0065-1/03</title>
 <style type="text/css">
 table td,table th{padding:0}
 BODY.body{background-color:#ffffff; max-width:468pt; padding:72pt 72pt 72pt 72pt}
@@ -9,23 +9,23 @@
 P.wrds{margin-bottom:0; margin-top:0; margin-left:36pt; margin-right:0; padding-top:0pt; color:#000000; font-size:11pt; padding-bottom:12pt; font-family:"Times New Roman","Times",serif; line-height:1.15; orphans:2; widows:2; text-align:left; font-weight:4
00; text-decoration:none; vertical-align:baseline; font-style:normal}
 P.text{margin-bottom:0; margin-top:0; margin-left:0; margin-right:0; padding-top:0pt; color:#000000; font-size:11pt; padding-bottom:0pt; font-family:"Arial","Liberation Sans",sans-serif; line-height:1.15; text-align:left; font-weight:400; text-decoration:
none; vertical-align:baseline; font-style:normal}
 P.txts{margin-bottom:0; margin-top:0; margin-left:0; margin-right:0; padding-top:0pt; color:#000000; font-size:11pt; padding-bottom:11pt; font-family:"Arial","Liberation Sans",sans-serif; line-height:1.15; text-align:left; font-weight:400; text-decoration
:none; vertical-align:baseline; font-style:normal}
+P.from{margin-bottom:0; margin-top:0; margin-left:0; margin-right:0; padding-top:0pt; color:#000000; font-size:10pt; padding-bottom:0pt; font-family:"Arial","Liberation Sans",sans-serif; line-height:1.15; orphans:2; widows:2; text-align:left; font-weight:
400; text-decoration:none; vertical-align:baseline; font-style:none}
+P.time{margin-bottom:0; margin-top:0; margin-left:0; margin-right:0; padding-top:0pt; color:#000000; font-size:9pt; padding-bottom:9pt; font-family:"Arial","Liberation Sans",sans-serif; line-height:1.15; orphans:2; widows:2; text-align:left; font-weight:4
00; text-decoration:none; vertical-align:baseline; font-style:italic}
+SPAN.name{font-family:"Lucida Calligraphy",cursive; font-style:normal}
 SPAN.ins{color:#007700}
 SPAN.del{color:#cc8888}
 P.l3h{margin-bottom:0; margin-top:0; margin-left:0; margin-right:0;color:#000000;font-size:26pt;font-family:"Arial","Liberation Sans",sans-serif; padding-top:0pt; padding-bottom:3pt; line-height:1.15; page-break-after:avoid; orphans:2; widows:2; text-alig
n:left; font-weight:400; text-decoration:none; vertical-align:baseline; font-style:normal}
 P.yox{margin-bottom:0; margin-top:0; margin-left:-3pt; margin-right:-22pt;color:#000000;font-size:7.5pt;font-family:"Arial","Liberation Sans",sans-serif; padding-top:2pt; padding-bottom:0pt; line-height:1.15; orphans:2; widows:2; text-align:left; font-wei
ght:400; text-decoration:none; vertical-align:baseline; font-style:normal}
-P.z5n{margin-bottom:0; margin-top:0; margin-left:20pt; margin-right:0;color:#000000;font-size:11pt;font-family:"Times New Roman","Times",serif; padding-top:0pt; padding-bottom:7pt; line-height:1.330909090909091; orphans:2; widows:2; text-align:left; font-
weight:400; text-decoration:none; vertical-align:baseline; font-style:normal}
-P.kjh{margin-bottom:0; margin-top:0; margin-left:20pt; margin-right:0;color:#000000;font-size:11pt;font-family:"Times New Roman","Times",serif; padding-top:0pt; padding-bottom:7pt; line-height:1.330909090909091; orphans:2; widows:2; text-align:left; font-
weight:400}
-P.eaj{margin-bottom:0; margin-top:0; margin-left:0; margin-right:0;color:#000000;font-size:11pt;font-family:"Arial","Liberation Sans",sans-serif; padding-top:0pt; padding-bottom:7pt; line-height:1.330909090909091; orphans:2; widows:2; text-align:left; fon
t-weight:400; text-decoration:none; vertical-align:baseline; font-style:normal}
 SPAN.jas{background-color:#fffff0}
 P.s2p{margin-bottom:0; margin-top:0; margin-left:65pt; margin-right:0;color:#000000;font-size:9.5pt;font-family:"Times New Roman","Times",serif; padding-top:0pt; padding-bottom:6pt; line-height:1.232842105263158; orphans:2; widows:2; text-align:left; font
-weight:400}
 SPAN.ehd{text-decoration:none; vertical-align:baseline;font-style:normal}
-P.rcw{margin-bottom:0; margin-top:0; margin-left:36pt; margin-right:0; color:#000000; font-size:11pt; font-family:"Times New Roman","Times",serif; padding-top:0pt; padding-bottom:13pt; line-height:1.15; orphans:2; widows:2; text-align:left; font-weight:40
0}
 </style>
 </head><body class="body"><p class="l3h">AI22-0065-1</p>
-<p class="head">!standard C(1) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
+<p class="head">!standard 1.1.2(17) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;23-05-29 &nbsp;AI22-0065-1/02</p>
-<p class="head">!standard D(1)</p>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;23-09-07 &nbsp;AI22-0065-1/03</p>
+<p class="head">!standard 1.1.3(16/5)</p>
+<p class="head">!standard 1.1.3(17/3)</p>
 <p class="head">!class binding interpretation 23-03-22</p>
 <p class="head">!status Corrigendum 1-2022 &nbsp;23-06-27</p>
 <p class="head">!status ARG Approved &nbsp;10-0-0 &nbsp;23-06-11</p>
@@ -45,29 +45,31 @@
 requirements&quot;, like those given in the Specialized Needs Annexes, do not make the annexes
 normative.</p>
 
-<p class="txts">Our intent has been that anything that implementers are supposed to follow should
+<p class="text">Our intent has been that anything that implementers are supposed to follow should
 be normative. Thus, the fact that the Specialized Needs Annexes cannot be normative is
-uncomfortable. One way to make them normative might be to organize them more like Annex B, with a
-small required part and a larger optional part.</p>
+uncomfortable.</p>
+<h2 class="head">!recommendation</h2>
+<p class="txts">One way to make the Specialized Needs Annexes normative might be to organize them
+more like Annex B, with a small required part and a larger optional part.</p>
 
 <p class="txts">Alternatively, we could simply drop the whole distinction between optional and
 non-optional requirements, since there is not a general rule that an ISO standard is
 all-or-nothing, despite the all-or-nothing history of the Ada standard. Instead, we can indicate
 that conformance for the core and each annex are defined separately. The C standard does something
 similar, where they have two forms of conformance, a &ldquo;conforming hosted implementation&rdquo;
-and a &ldquo;conforming freestanding implementation.&rdquo;</p>
+and a &ldquo;conforming freestanding implementation&rdquo;.</p>
 
 <p class="txts">The most relevant paragraphs are the following:</p>
 
-<p class="txts">RM 1.1.2(17):</p>
+<p class="txts">1.1.2(17):</p>
 
-<p class="rcw">All implementations shall conform to the core language. In addition, an
+<p class="wrds">All implementations shall conform to the core language. In addition, an
 implementation may conform separately to one or more Specialized Needs
 Annexes.<span class="jas">&nbsp; &hellip;</span></p>
 
-<p class="text">and RM 1.1.3(16/5-17/3):</p>
+<p class="text">and 1.1.3(16/5-17/3):</p>
 <p class="yox">16/5</p>
-<p class="z5n">An implementation that conforms to this Reference Manual shall support each
+<p class="word">An implementation that conforms to this Reference Manual shall support each
 capability required by the core language as specified. In addition, an implementation that conforms
 to this Reference Manual may conform to one or more Specialized Needs Annexes (or to none).
 Conformance to a Specialized Needs Annex means that each capability required by the Annex shall be
@@ -77,7 +79,7 @@
 that an implementation conforms to a Specialized Needs Annex, namely, only by supporting all
 capabilities required by the Annex. </span></p>
 <p class="yox">17/3</p>
-<p class="kjh">An implementation conforming to this Reference Manual may provide additional
+<p class="word">An implementation conforming to this Reference Manual may provide additional
 aspects, attributes, library units, and pragmas. However, it shall not provide any aspect,
 attribute, library unit, or pragma having the same name as an aspect, attribute, library unit, or
 pragma (respectively) specified in a Specialized Needs Annex unless the provided construct is
@@ -86,14 +88,12 @@
 either be identified by the implementation before run time or shall raise an exception at run time.
 </p>
 <p class="text">We propose to modify this wording to treat conformance to the annexes more on the
-same level as conformance to the core. &nbsp;The two are now more independent of one another.</p>
-<h2 class="head">!recommendation</h2>
-<p class="text">(See Summary.)</p>
+same level as conformance to the core. The two are now more independent of one another.</p>
 <h2 class="head">!wording</h2>
-<p class="inst">Replace RM 1.1.2(17) with the following:</p>
+<p class="inst">Replace 1.1.2(17) with the following:</p>
 <p class="word">Conformance is defined separately for the core language and each of the Specialized
 Needs Annexes (see 1.1.3).</p>
-<p class="inst">Modify RM 1.1.3(16/5-17/3) as follows:</p>
+<p class="inst">Modify 1.1.3(16/5-17/3) as follows:</p>
 <p class="wrds">An implementation that conforms to
 <span class="del">[this]</span><span class="ins">{the <i>core</i> of this}</span> Reference Manual
 shall support each capability required by the core language <span class="ins">{(see 1.1.2),}</span>
@@ -113,15 +113,15 @@
 Annex]</span> shall either be identified by the implementation before run time or shall raise an
 exception at run time. </p>
 <h2 class="head">!discussion</h2>
-<p class="eaj">After reviewing other ISO standards, it seemed that there was no problem defining
+<p class="text">After reviewing other ISO standards, it seemed that there was no problem defining
 different levels of conformance. Therefore, we have tried to separate conformance to the
 &ldquo;core&rdquo; and the Specialized Needs Annexes, but generally treat them equivalently in
 terms of conformance, rather than making a special case of the core.</p>
 <h2 class="head">!ACATS test</h2>
-<p class="txts">Changing the status of Specialized Needed Annexes does not directly change any
-ACATS tests (ACATS tests can test optional requirements by the definition in ISO/IEC 18009).
-However, anything required of Ada implementations by the rewrite of the annexes may require
-existing tests to change their pass/fail criteria.</p>
+<p class="txts">Changing the status of Specialized Needs Annexes does not directly change any ACATS
+tests (ACATS tests can test optional requirements by the definition in ISO/IEC 18009). However,
+anything required of Ada implementations by the rewrite of the annexes may require existing tests
+to change their pass/fail criteria.</p>
 
 <p class="text">The ACATS currently treats the conformance of each annex separately, so the
 proposed changes would not have much impact on the ACATS. The ACATS does not attempt to test
@@ -129,6 +129,20 @@
 need to change with these changes. (It could change if there was sufficient interest and support,
 of course, but there would not be a requirement to find such support.)</p>
 <h2 class="head">!appendix</h2>
+<p class="from">From:<span class="name"> Randy Brukardt</span></p>
+<p class="time">Sent: Thursday, September 7, 2023 &nbsp;5:46 PM</p>
+
+<p class="txts">The !issue in version /02 of this AI rambles on about possible ways to fix the
+problem (as opposed to just presenting the problem). That is inappropriate for an !issue. As an
+editorial review change, I moved the extra text to the !recommendation (getting rid of &ldquo;see
+summary&rdquo;, of course). It probably would have been better to put the ways to fix the problem
+into the !discussion, but that would have required a lot of rewording and reorganization that is
+best avoided for an approved AI.</p>
+
+<p class="txts">There are also a number of other editorial review changes, most noted by John
+Barnes.</p>
+
+<hr><p class="txts">&nbsp;</p>
 
 
 </body></html> 

Questions? Ask the ACAA Technical Agent