This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [PATCH] Add header implementation of std::to_string for integers (PR libstdc++/71108)
- From: Daniel Krügler <daniel dot kruegler at gmail dot com>
- To: Adrian Wielgosik <adrian dot wielgosik at gmail dot com>
- Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>, gcc-patches List <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 28 May 2017 22:03:33 +0200
- Subject: Re: [PATCH] Add header implementation of std::to_string for integers (PR libstdc++/71108)
- Authentication-results: sourceware.org; auth=none
- References: <CAPoJ1RH7BDKNCF9yo8XEXx_mSZ4=G2LWPxxG0rfL9oSyrQSUWQ@mail.gmail.com> <CAGNvRgB6HeX2kT+PZM1stppJMZ_y-=nkGt9BjKgUm0gruTF92g@mail.gmail.com> <CAPoJ1RHDP41LqWvyUB1Sko=-sM5=tw2Hc-Cyh_HoJ90Ee3fOeA@mail.gmail.com>
2017-05-28 21:38 GMT+02:00 Adrian Wielgosik <adrian.wielgosik@gmail.com>:
>> so a conforming program could notice the difference by either calling std::setlocale.
>
> Unless I missed or misunderstood something about locale (please let me
> know if I did), I don't know of any way for locale to affect %d and
> its integer friends.
Hmmh, rethinking about it, I agree that I also cannot see a possible
effect here for the integer types. Initially I was alarmed by the fact
alone that the current wording is basically local-depending, but now I
agree that in this case I cannot find how a conforming program could
observe the difference. Thanks for remaining stubbornly ;-)
- Daniel