Skip to content
This repository has been archived by the owner on Mar 26, 2024. It is now read-only.

string->number should not signal error #322

Closed
dcurrie opened this issue Jan 10, 2016 · 0 comments
Closed

string->number should not signal error #322

dcurrie opened this issue Jan 10, 2016 · 0 comments

Comments

@dcurrie
Copy link
Contributor

dcurrie commented Jan 10, 2016

R7RS says: If string is not a syntactically valid notation for a number, or would result in a number that the implementation cannot represent, then string->number returns #f. An error is never signaled due to the content of string.

> (string->number "-e3")
error: invalid string given: -e3
> (string->number "-e3e4")
error: invalid string given: -e3e4
> (string->number "-")
error: invalid string given: -

BTW, this defect pre-dates the ATOD DTOA changes.

I have a patch coming to fix this defect.

dcurrie added a commit to dcurrie/picrin that referenced this issue Jan 10, 2016
nyuichi added a commit that referenced this issue Jan 12, 2016
Fix issue #322 string->number should never signal error
@dcurrie dcurrie closed this as completed Jan 24, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant