Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anemone's strtod still not on par with Double parser in Attoparsec #48

Open
erikd-ambiata opened this issue Mar 7, 2017 · 1 comment

Comments

@erikd-ambiata
Copy link
Contributor

Looking again at using Anemone in Walrus to parse Double values and find that stdtod fails on
strings like1.e1and 12. where there the . character is either at the end of the string or just preceding the exponent.

@amosr
Copy link
Contributor

amosr commented Mar 7, 2017

Yeah, I guess we should aim to match whatever libc strtod does. I wonder whether there's a standard for what is and is not valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants