Christian Reis <kiko@async.com.br> writes: > > I added the special-casing of LC_NUMERIC when I found Python can't > > parse floating point literals in Python source code anymore, in such a > > locale (de_DE uses the same convention). This is triggered by atof(3) > > changing its meaning, inside compile.c:parsenumber. > > Is there a good reason to prefer atof() over strtod(), if we already > have a locale-safe version of the latter? I don't think so - it is the same on systems where strtod is supported. However, I think Python uses atof since strtod might not be available. 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