"Tim Peters" <tim.one at comcast.net> writes: > > This is much worse, then: How can it possibly know what formats the C > > library expects in the current locale? What if the C library insists that > > a thousands-separator is used when the locale has one? etc. > > I'm not sure that's a realistic objection. Ok. Are you then, overall, in favour of taking the proposed approach? It is not thread-safe, but only so if somebody calls setlocale in a different thread, and that is known not to be thread-safe - so I could live with that limitation. It is just that the patch does not "feel" right, given that there must be "native" locale-inaware parsing of floating point constants somewhere on each platform (atleast on those that support C++98). Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4