<font size=2 face="sans-serif">ISSUE 4: Do we need to do add wide character
strfrom functions (freestanding implementations are not required to support
wide characters)?</font>
<br>
<br><font size=2 face="sans-serif">My opinion is yes as for worldwide adoption,
wide characters are common. This does makes it harder to implement which
may reduce adoption though.</font>
<br>
<br><font size=2 face="sans-serif">ISSUE 5: Is it appropriate for this
floating-point TS to specify integer strfrom functions?</font>
<br>
<br><font size=2 face="sans-serif">My opinion is no. We should focus on
floating point types and not the integer types. Allowing this may impose
a burden or otherwise hinder implementers (ex. DSP chips).</font>
<br>
<br><font size=2 face="sans-serif">ISSUE 6: The macro names FP_CEIL, etc.
might suggest results will be in floating types.</font>
<br>
<br><font size=2 face="sans-serif">I agree with the proposed change.</font>
<br>
<br><font size=2 face="sans-serif">Rajan</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Jim Thomas <jaswthomas@sbcglobal.net></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">CFP <cfp-interest@ucbtest.org></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">04/10/2012 07:37 PM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">[Cfp-interest] outstanding issues</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">cfp-interest-bounces@oakapple.net</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=4>Greetngs all,<br>
<br>
Below is a list of outstanding issues for the CFP draft TS Part 1. Email
discussion in advance of our teleconference next week (4/19) would improve
the chances of resolving the issues during the meeting.</font>
<p><font size=4>-Jim<br>
<br>
<br>
ISSUE 1: Is requiring freestanding support for part of a header ok?<br>
<br>
The partial header approach was proposed by a member of WG14 (the C committee)
and we've had no response from others on WG14 about it. Unless CFP has
an issue with it, I suggest we leave it to WG14 to object if they wish.<br>
<br>
<br>
ISSUE 2: Make F.1 more readable.<br>
<br>
Here's F.1 broken into three paragraphs, which I think helps some:</font>
<p><font size=4>This annex specifies C language support for the IEC 60559
floating-point standard. The IEC 60559 floating-point standard is specifically
Floating-point arithmetic (ISO/IEC/IEEE 60559:2011), also designated as
IEEE Standard for Floating-Point Arithmetic (IEEE 754−2008). The IEC
60559 floating-point standard supersedes the IEC 60559:1989 binary arithmetic
standard, also designated as IEEE Standard for Binary Floating-Point Arithmetic
(IEEE 754−1985). IEC 60559 generally refers to the floating-point standard,
as in IEC 60559 operation, IEC 60559 format, etc.<br>
<br>
The IEC 60559 floating-point standard specifies decimal, as well as binary,
floating-point arithmetic. It supersedes IEEE Standard for Radix-Independent
Floating-Point Arithmetic (ANSI/IEEE 854−1987), which generalized the
binary arithmetic standard (IEEE 754-1985) to remove dependencies on radix
and word length.<br>
<br>
An implementation that defines __STDC_IEC_60559_BFP__ to 201ymmL shall
conform to the specifications in this annex.356) Where a binding between
the C language and IEC 60559 is indicated, the IEC 60559-specified behavior
is adopted by reference, unless stated otherwise.<br>
<br>
<br>
ISSUE 3: Would it be better to restrict the format specifiers that the
strfrom functions have to support?<br>
<br>
>From Rajan:<br>
<br>
Replace<br>
<br>
NOTE If the conversion specifier (in the string pointed to
by format) for x is not applicable to type double or long double, the behavior
of strfromd or strfromld, respectively, is undefined.<br>
<br>
with<br>
<br>
NOTE The format string must support specifying the precision, the
floating point conversion specifiers (a, A, e, E, f, F, g, G), and the
length modifier (L). An implementation may add any other format string
support. If any other format string not explicitly supported by the implementation
is present, the behaviour is undefined.<br>
<br>
Recommended practice: The equivalent of hosted support for conversion specifiers
for snprintf should be allowed.<br>
<br>
I think the question here is whether the simplicity achieved is worth the
formatting functionality lost? Think of adapting Tydeman suite for freestanding.<br>
</font>
<p><font size=4>ISSUE 4: Do we need to do add wide character strfrom functions
(freestanding implementations are not required to support wide characters)?<br>
<br>
If CFP doesn't have a strong opinion, we might leave this as an issue for
WG14.</font>
<p><font size=4><br>
ISSUE 5: Is it appropriate for this floating-point TS to specify integer
strfrom functions?<br>
<br>
Do freestanding implementations already have functions that convert integers
to character sequences? atoi? <br>
<br>
<br>
ISSUE 6: The macro names FP_CEIL, etc. might suggest results will be in
floating types.<br>
<br>
How about FP_INT_UPWARD, etc.? These: indicate that integers are involved
and don’t refer to ceil so don't suggest conversion to floating type;
are different enough from FE_UPWARD, etc. to avoid mixing them up; start
with FP like most other macros in math.h; and aren't too terribly long.<br>
<br>
<br>
ISSUE 7: Should the 7.12 specification of llogb require a domain error
for finite out-of-range cases? Waiting for C committee resolution of a
DR about the same issue for ilogb.</font>
<p><font size=4>This is resolved, for now.<br>
<br>
<br>
ISSUE 8: Forward references need to be added throughout.<br>
</font><tt><font size=2>_______________________________________________<br>
Cfp-interest mailing list<br>
Cfp-interest@oakapple.net<br>
</font></tt><a href="http://mailman.oakapple.net/mailman/listinfo/cfp-interest"><tt><font size=2>http://mailman.oakapple.net/mailman/listinfo/cfp-interest</font></tt></a><tt><font size=2><br>
</font></tt>
<p>
<p>