<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Another item from WG14 that will be added to our Agenda for the May meeting.</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="ms-outlook-mobile-signature">
<p class="xxmsonormal" style="margin: 0in;"><span style="color: rgb(33, 33, 33);">Regards,<br>
<br>
<b>Rajan Bhakta</b><br>
</span> </p>
</div>
<div id="mail-editor-reference-message-container">
<div class="ms-outlook-mobile-reference-message skipProofing">
<meta name="Generator" content="Microsoft Exchange Server">
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="text-align: left; padding: 3pt 0in 0in; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor; font-family: Aptos; font-size: 12pt; color: black;">
<b>From: </b>owner-sc22wg14@open-std.org <owner-sc22wg14@open-std.org> on behalf of Joseph Myers <josmyers@redhat.com><br>
<b>Date: </b>Monday, May 11, 2026 at 11:45 AM<br>
<b>To: </b>sc22wg14@open-std.org <sc22wg14@open-std.org><br>
<b>Subject: </b>[EXTERNAL] [SC22WG14.36469] Annex H and non-arithmetic interchange formats<br>
<br>
</div>
<div class="PlainText" style="font-size: 11pt;">I don't think I've seen any comments from CFP on this issue I raised in<br>
October. Maybe CFP missed this message?<br>
<br>
--<br>
Joseph S. Myers<br>
josmyers@redhat.com<br>
<br>
On Thu, 23 Oct 2025, Joseph Myers wrote:<br>
<br>
> Some of the rules in Annex H for when functions should be declared,<br>
> conditional on support for non-arithmetic interchange formats, seem rather<br>
> odd. Are these rules as intended or is there a mistake here?<br>
><br>
> H.11.4.1 says "Implementations that do not support non-arithmetic<br>
> interchange formats are not required to declare the functions in this<br>
> subclause." (that is, the encoding conversion functions; I think "this<br>
> subclause" must mean H.11.4). Obviously that makes sense for such<br>
> functions *for such non-arithmetic formats*. But what about such<br>
> functions for arithmetic formats?<br>
><br>
> * encodefN and decodefN use the _FloatN type; that is, they only make<br>
> sense for arithmetic formats. But they're in H.11.4, suggesting that in<br>
> the absence of non-arithmetic formats, those functions need not be<br>
> supported for arithmetic formats either. Furthermore, the corresponding<br>
> functions for decimal types have no such restriction.<br>
><br>
> * fMencfM, dMencdecdN and dMencbindN are described in H.11.4.3.1 as being<br>
> declared for all supported pairs of (unequal) M and N, both arithmetic and<br>
> non-arithmetic. But the above quoted statement would suggest that in the<br>
> absence of non-arithmetic formats, none of them are supported even for<br>
> arithmetic formats.<br>
><br>
> * The string-from-encoding and string-to-encoding functions in H.12.4 and<br>
> H.12.5 also apply for both arithmetic and non-arithmetic formats. But as<br>
> they aren't part of H.11.4, the wording from H.11.4.1 doesn't apply to<br>
> them. So those functions, unlike the direct encoding conversion<br>
> functions, seem to be required for all supported arithmetic formats<br>
> regardless of whether any non-arithmetic formats are supported.<br>
><br>
> --<br>
> Joseph S. Myers<br>
> josmyers@redhat.com<br>
<br>
</div>
</div>
</body>
</html>