v1.0.0 Stable API Release #3
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- introducing new api - code clean - to_perl_object
Conflicts: lib/JavaScript/Duktape.pm
This is a simple benchmark for checking during v1.0.0 development release, we need things to be as fast ass possible
Owner
Author
|
reopened with #4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This new release is toward stabilizing and introduce new API
The new API mainly
to_perl_objectwill provide a new way to call javascript objects from perl, where we will be able to get javascript objects and use them from perl the exact way they are used in javascript land.Another issue to address is circular references, the current behavior is that we store perl subs in global hash to avoid being garbage collected while still needed by javascript, this will make it a memory hog once we try to push hundreds of perl functions, this version will introduce a fix for this problem by using duktape internal object finalizers, this solution will make things a little bit slower but much better with memory usage, there are some other ideas to fix this issue but at this stage object finalizes seems a good solution.