Skip to content

Stream parseInt() and parseFloat() functions should have an option to not search ahead. [imported] #630

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.

Sign up for GitHub

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

Jump to bottom
Closed
cmaglie opened this issue Nov 15, 2012 · 3 comments
Closed

Stream parseInt() and parseFloat() functions should have an option to not search ahead. [imported] #630

cmaglie opened this issue Nov 15, 2012 · 3 comments
Assignees
@cmaglie
Milestone
Release 1.6.7

Comments

@cmaglie
Copy link
Member

cmaglie commented Nov 15, 2012

This is Issue 630 moved from a Google Code project.
Added by 2011-09-08T18:45:08.000Z by dmel...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.

Original labels: Type-Enhancement, Priority-Medium, Component-Core

Original description

I'd like to add a parameter to these functions (or some other method) that tells them not to skip ahead in the stream data to find the next number. Ideally, there should be three options: don't skip anything, only skip whitespace, and skip anything. Maybe SKIP_NONE, SKIP_ALL, SKIP_NONE.
@ffissore ffissore added the New label Feb 27, 2014
@aop
Copy link

aop commented Apr 14, 2014

This would be a very good feature. Any progress?

@Chris--A Chris--A mentioned this issue Jun 19, 2015
Closed
@Chris--A
Copy link
Contributor

An implementation for this has been proposed in #3337

@sandeepmistry sandeepmistry added this to the Release 1.6.7 milestone Nov 23, 2015
@sandeepmistry
Copy link
Contributor

Resolved by #3337.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cmaglie cmaglie

Labels
None yet
Projects
None yet
Milestone
Release 1.6.7
Development

No branches or pull requests
6 participants
@matthijskooijman @aop @cmaglie @ffissore @sandeepmistry @Chris--A