Leo Wang

I can try to fix the last case first

Due to the streaming nature of JsonSurfer, Case 2 and 3 with negative step are very hard to implement

Cool. It does make sense. I will try.

I've just reviewed source code and couldn't figure out a quick fix. So Case 2 & 3 won't be supported in near release

Thanks so much for reporting. I'll examine the code to see if any quick fix on this.

@enridaga the first working implementation just submitted. Please feel free to pull the source and test

JsonSurfer is built upon those streaming api, not really competing with them

Did you test it? Are sure no any exception would be thrown when calling nextString() following "NUMBER" token?

I think it would introduce too much overhead for the potential two more parsing. If you really need long type, I think you can implement a custom JsonProvider.

Actually, I'm curious about your use case? What kind of benefit can you gain from such conversion?