<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);">
In reverse order, this is probably not a good item for the wording study group as they focus on fixing minor wording mistakes and matching existing standard wording for papers that are intended to be accepted by the committee. This item is more of a new proposal
which would need direction on what to say while they would deal with making the “How” exact once we got close.</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
With regards to whether we need to tidy it up, we certainly could take on this item as it does fit into our groups purpose.</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>cfp-interest <cfp-interest-bounces@oakapple.net> on behalf of Damian McGuckin <damianm@esi.com.au><br>
<b>Date: </b>Saturday, April 18, 2026 at 6:05 AM<br>
<b>To: </b>CFP Interest <cfp-interest@oakapple.net><br>
<b>Subject: </b>[EXTERNAL] [cfp-interest 3899] Converison Between Real Floating Types - 6.3.2.5<br>
<br>
</div>
<div class="PlainText" style="font-size: 11pt;"><br>
Courtesy of Jan Schultke.<br>
<br>
On being forced to read these clauses,<br>
<br>
When a value of real floating type is converted to a standard floating<br>
type, if the value being converted is in the range of values that can be<br>
represented but cannot be represented exactly, the result is either the<br>
nearest higher or nearest lower representable value, chosen in an<br>
implementation-defined manner. If the value being converted is outside<br>
the range of values that can be represented, the behavior is undefined<br>
<br>
When a value of real floating type is converted to a decimal floating<br>
type, if the value being converted cannot be represented exactly, the<br>
result is correctly rounded with exceptions raised as specified in<br>
ISO/IEC 60559.<br>
<br>
I noticed the second uses totally different language to the second. Isn't<br>
the former also talking about rounding according to the some mode. Also,<br>
the second makes mention of the exceptions raised, e.g. inexact, overflow,<br>
underflow or some combination.<br>
<br>
Do we need to tidy that up?<br>
<br>
Is this a perfect case for the new WG14 wording study group?<br>
<br>
Thanks - Damian<br>
_______________________________________________<br>
cfp-interest mailing list<br>
cfp-interest@oakapple.net<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.oakapple.net_mailman_listinfo_cfp-2Dinterest&d=DwICAg&c=BSDicqBQBDjDI9RkVyTcHQ&r=XTIN0AwPKAf2bIKNxlzdeqggAytE5h-JEusWpx9MXwc&m=cXdu-5gMAinTbb9bNYPL3aiISnXA-MMgFEyxznyK3CNwb0WGDg42DaKNF4RuHz1I&s=vHn4-bMQbHtaCCxgrj3o-S3xH-zu5EuzGUOzr_PIS7g&e=" data-outlook-id="e4018d66-9c26-4d9d-986d-564c02db2fa8">https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.oakapple.net_mailman_listinfo_cfp-2Dinterest&d=DwICAg&c=BSDicqBQBDjDI9RkVyTcHQ&r=XTIN0AwPKAf2bIKNxlzdeqggAytE5h-JEusWpx9MXwc&m=cXdu-5gMAinTbb9bNYPL3aiISnXA-MMgFEyxznyK3CNwb0WGDg42DaKNF4RuHz1I&s=vHn4-bMQbHtaCCxgrj3o-S3xH-zu5EuzGUOzr_PIS7g&e=</a><br>
</div>
</div>
</body>
</html>