This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Poor me... (was: Re: [PATCH, RFA] Reworked fix for PR4402)


Phil Edwards wrote:

> On Sun, Dec 02, 2001 at 01:17:58AM +0000, Nathan Myers wrote:
> > The Standard requires parsing separators in floats, and there is no
> > prospect of that changing.  The official status of the Defect Report
> > is still "Open"; resolution has been stalled for years by several
> > members of the LWG, but they can't put it off forever.
>
> For the record:  which DR is this?  (A cursory search didn't find anything
> with an obvious name.)

Hi Phil. In the meanwhile I have found it: it is #282.

Cheers,
P.

/////////////////////////////

282. What types does numpunct grouping refer to?

Section: 22.2.2.2.2 [lib.facet.num.put.virtuals]  Status: Open  Submitter: Howard Hinnant
Date: 5 Dec 2000

Paragraph 16 mistakenly singles out integral types for inserting thousands_sep()
characters. This conflicts with the syntax
for floating point numbers described under 22.2.3.1/2.

Proposed resolution:

Change paragraph 16 from:

     For integral types, punct.thousands_sep() characters are inserted into the sequence
as determined by the value
     returned by punct.do_grouping() using the method described in 22.2.3.1.2
[lib.facet.numpunct.virtuals].

To:

     For arithmetic types, punct.thousands_sep() characters are inserted into the sequence
as determined by the
     value returned by punct.do_grouping() using the method described in 22.2.3.1.2
[lib.facet.numpunct.virtuals].

[ Copenhagen: Opinions were divided about whether this is actually an inconsistency, but
at best it seems to have been
unintentional. This is only an issue for floating-point output: The standard is
unambiguous that implementations must
parse thousands_sep characters when performing floating-point. The standard is also
unambiguous that this requirement
does not apply to the "C" locale. ]

[ A survey of existing practice is needed; it is believed that some implementations do
insert thousands_sep characters for
floating-point output and others fail to insert thousands_sep characters for
floating-point input even though this is
unambiguously required by the standard. ]

///////////////////////////////////////////



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]