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

Differences between 1.2 and version 1.3
Log of other versions for file ai22s/ai22-0039-1.html

--- ai22s/ai22-0039-1.html	2022/06/17 06:15:52	1.2
+++ ai22s/ai22-0039-1.html	2022/06/17 06:22:44	1.3
@@ -1,10 +1,10 @@
-<html><head><meta content="text/html; charset=UTF-8" http-equiv="content-type"><title>AI22-0039-1/02</title>
+<html><head><meta content="text/html; charset=UTF-8" http-equiv="content-type"><title>AI22-0039-1/03</title>
 <style type="text/css">
 table td,table th{padding:0}
-.c1{color:#000000;font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:"Times New Roman";font-style:normal}
-.c2{background-color:#ffffff;max-width:468pt;padding:72pt 72pt 72pt 72pt}
-.c12{font-weight:400;font-family:"Arial"}
-.c8{border:1px solid black;margin:5px}
+.c8{color:#000000;font-weight:400;text-decoration:none;vertical-align:baseline;font-size:11pt;font-family:"Times New Roman";font-style:normal}
+.c9{background-color:#ffffff;max-width:468pt;padding:72pt 72pt 72pt 72pt}
+.c12{border:1px solid black;margin:5px}
+.c10{font-weight:400;font-family:"Arial"}
 P.head{margin-bottom:0; margin-top:0; margin-left:0; margin-right:0; padding-top:0pt; color:#000000; font-size:14pt; 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:normal}
 H2.head{margin-bottom:0; margin-top:0; margin-left:0; margin-right:0; padding-top:12pt; color:#000000; font-size:14pt; padding-bottom:6pt; font-family:"Arial","Liberation Sans",sans-serif; line-height:1.15; page-break-after:avoid; orphans:2; widows:2; tex
t-align:left; font-weight:400; text-decoration:none; vertical-align:baseline; font-style:normal}
 P.inst{margin-bottom:0; margin-top:0; margin-left:18pt; margin-right:0; padding-top:9pt; color:#000000; font-size:12pt; padding-bottom:6pt; font-family:"Arial","Liberation Sans",sans-serif;line-height:1.15; orphans:2; widows:2; text-align:left; font-weigh
t:400; text-decoration:none; vertical-align:baseline; font-style:normal}
@@ -18,11 +18,13 @@
 SPAN.del{color:#880000}
 P.a1{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-align
:left; font-weight:400; text-decoration:none; vertical-align:baseline; font-style:normal}
 </style>
-</head><body class="c2"><p class="a1">AI22-0039-1</p>
+</head><body class="c9"><p class="a1">AI22-0039-1</p>
 <p class="head">!standard 8.3(26/2) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;22-04-25 &nbsp;AI22-0039-1/02</p>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;22-06-14 &nbsp;AI22-0039-1/03</p>
 <p class="head">!class presentation 22-02-04</p>
+<p class="head">!status Corrigendum 1-2022 22-06-14</p>
+<p class="head">!status ARG Approved 22-05-05</p>
 <p class="head">!status work item 22-02-04</p>
 <p class="head">!status received 21-05-20</p>
 <p class="head">!priority Low</p>
@@ -46,7 +48,7 @@
 
 <p class="wrds">A nonoverridable declaration is illegal if there is a homograph occurring
 immediately within the same declarative region that is visible at the place of the declaration, and
-is not hidden from all visibility by the non-overridable declaration. <span class="ins">{This rule
+is not hidden from all visibility by the nonoverridable declaration. <span class="ins">{This rule
 also applies to dispatching operations declared in the visible part of an instance of a generic
 unit. However, it does not apply to other overloadable declarations in an instance; such
 declarations may have type conformant profiles in the instance, so long as the corresponding
@@ -55,12 +57,12 @@
 <p class="wrds"><span class="ins">}</span><span class="del">[In addition,
 a]</span><span class="ins">{A}</span> type extension is illegal if somewhere within its immediate
 scope it has two visible components with the same name. <span class="del">[Similarly,
-the]</span><span class="ins">{The}</span> <span class="c12">context_clause</span> for a compilation
-unit is illegal if it mentions (in a <span class="c12">with_clause</span>) some library unit, and
+the]</span><span class="ins">{The}</span> <span class="c10">context_clause</span> for a compilation
+unit is illegal if it mentions (in a <span class="c10">with_clause</span>) some library unit, and
 there is a homograph of the library unit that is visible at the place of the compilation unit, and
 the homograph and the mentioned library unit are both declared immediately within the same
 declarative region.
-&nbsp;<sup><a href="#cmnt1"><span class="del">[a]</span></a></sup><sup><a href="#cmnt2"><span class="del">[b]</span></a></sup><sup><a href="#cmnt3"><span class="del">[c]</span></a></sup><sup><a href="#cmnt4"><span class="del">[d]</span></a></sup><span cla
ss="c1"><span class="del">[These
+&nbsp;<sup><a href="#cmnt1"><span class="del">[a]</span></a></sup><sup><a href="#cmnt2"><span class="del">[b]</span></a></sup><sup><a href="#cmnt3"><span class="del">[c]</span></a></sup><sup><a href="#cmnt4"><span class="del">[d]</span></a></sup><span cla
ss="c8"><span class="del">[These
 rules also apply to &nbsp;dispatching operations declared in the visible part of an instance of a
 generic unit. However, they do not apply to other overloadable declarations in an instance; such
 declarations may have type conformant profiles in the instance, so long as the corresponding
@@ -149,19 +151,59 @@
 <p class="text">old (Ada 2005) text. Thus this suggestion is out of bounds for this review and</p>
 <p class="txts">it is marked deferred.</p>
 
+<p class="txts">****************************************************************</p>
+
+<p class="from">From:<span class="name"> Tucker Taft</span></p>
+<p class="time">Sent: Thursday, April 14, 2022 &nbsp;9:09 AM </p>
+
+<p class="txts">(as comment on AI wording)</p>
+
+<p class="txts">Might be better: &quot;The rules given above that apply to subprograms
+...&quot;</p>
+
+<p class="txts">***************************************************************</p>
+
+<p class="from">From:<span class="name"> Randy Brukardt</span></p>
+<p class="time">Sent: Friday, April 15, 2022 &nbsp;10:18 PM</p>
+
+<p class="txts">Yes, but do we need it? I was unable to convince myself that the context clause
+rule could ever trigger for a dispatching operation. If &quot;these rules&quot; is really only one
+rule, rearranging the text would be better. I think that was the reason this was given to you as
+homework.</p>
+
+<p class="txts">****************************************************************</p>
+
+<p class="from">From:<span class="name"> Randy Brukardt</span></p>
+<p class="time">Sent: Friday, April 15, 2022 10:25 PM</p>
+
+<p class="txts">Expanding a bit: A context clause can mention a subprogram, but a library unit
+cannot be a dispatching operation. A stub could be a dispatching operation, but
+&quot;separate&quot; is NOT part of a context clause, so the rule doesn&#39;t apply there anyway
+(and wouldn&#39;t the stub be illegal if there was a problem?). So if only the first rule is really
+involved with &quot;these rules&quot;, then this sentence should just follow the first sentence
+with &quot;this rule also applies...&quot;. Right?</p>
+
+<p class="txts">****************************************************************</p>
+
+<p class="from">From:<span class="name"> Tucker Taft</span></p>
+<p class="time">Sent: Monday, April 25 &nbsp;12:56 PM</p>
+
+<p class="txts">Agreed. &nbsp;I have made that change, and have suggested a new paragraph for the
+following sentences.</p>
+
 <p class="text">****************************************************************</p>
-<div class="c8"><p class="text"><a href="#cmnt_ref1">[a]</a>Might be better: &quot;The rules given
+<div class="c12"><p class="text"><a href="#cmnt_ref1">[a]</a>Might be better: &quot;The rules given
 above that apply to subprograms ...&quot;</p>
-</div><div class="c8"><p class="text"><a href="#cmnt_ref2">[b]</a>Yes, but do we need it? I was
+</div><div class="c12"><p class="text"><a href="#cmnt_ref2">[b]</a>Yes, but do we need it? I was
 unable to convince myself that the context clause rule could ever trigger for a dispatching
 operation. If &quot;these rules&quot; is really only one rule, rearranging the text would be
 better. I think that was the reason this was given to you as homework.</p>
-</div><div class="c8"><p class="text"><a href="#cmnt_ref3">[c]</a>Expanding a bit: A context clause
-can mention a subprogram, but a library unit cannot be a dispatching operation. A stub could be a
-dispatching operation, but &quot;separate&quot; is NOT part of a context clause, so the rule
+</div><div class="c12"><p class="text"><a href="#cmnt_ref3">[c]</a>Expanding a bit: A context
+clause can mention a subprogram, but a library unit cannot be a dispatching operation. A stub could
+be a dispatching operation, but &quot;separate&quot; is NOT part of a context clause, so the rule
 doesn&#39;t apply there anyway (and wouldn&#39;t the stub be illegal if there was a problem?). So
 if only the first rule is really involved with &quot;these rules&quot;, then this sentence should
 just follow the first sentence with &quot;this rule also applies...&quot;. Right?</p>
-</div><div class="c8"><p class="text"><a href="#cmnt_ref4">[d]</a>Agreed.&nbsp; I have made that
+</div><div class="c12"><p class="text"><a href="#cmnt_ref4">[d]</a>Agreed.&nbsp; I have made that
 change, and have suggested a new paragraph for the following sentences.</p>
 </div></body></html> 

Questions? Ask the ACAA Technical Agent