-
Notifications
You must be signed in to change notification settings - Fork 525
Modularization #160
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
Comments
I would like to make this change as well. But I do not have time to work on this at the moment. If you want to contribute, just go ahead. |
If this will break existing API, will you accept such changes? |
We can start a V2 version. |
Ok. |
Any chance of bumping the version to Java 9 along with this change to support jigsaw modularity as well? I maintain a JDK 10 targeted fork of jsoniter with a module-info.java specified so that I can use this as part of a jlink build. |
Any way to add module-info without breaking Java 6 compatibility? |
No, I don't think it is possible. I only mentioned it because this would be a new version bump so I was hoping it might be a good opportunity to move forward. Also, forgot to mention, Java 9 has a supplied Base64 Encoder. |
Sadly, Android requires 1.6 bytecode, and this parser is very helpful there since You can just add module-info into your JAR. |
@Miha-x64 https://github.com/json-iterator/java-core invited you to host the development |
Hello.
I'm currently working on a library for Android which requires JSON parsing.
My requirements are:
— small methods count (DEX limit);
— small bytecode size (smaller APK and faster verification);
— high parsing speed.
I totally like your parser. I've took your streaming code, removed
<T>
parsing,Any
type, and some other unused stuff; inlined one-liners.My result is <50 methods and 10.8 KB DEX :)
I think it makes sense to move streaming to another module/artifact so those who need only streaming may use it without other parser parts.
The text was updated successfully, but these errors were encountered: