-
Notifications
You must be signed in to change notification settings - Fork 121
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
v8pp::set_const does not work in recent v8 versions (>6.0) #66
Comments
jcmonnin
changed the title
v8pp::set_const does not work recent v8 versions (>6.0)
v8pp::set_const does not work in recent v8 versions (>6.0)
Jan 20, 2018
Hi Jean-Claude, Thank you for raising this issue. Yes, I’ve already got the same a time ago. So pull request is welcomed. There was also a stalled branch I’m not sure what minimal V8 version support, 6.0 seems ok for me. |
pmed
added a commit
that referenced
this issue
Feb 4, 2018
Fixed issue #66 and removed outdated preprocessor definitions from Visual Studio global project properties.
Thanks for tackling the v8 API changes. |
pmed
added a commit
that referenced
this issue
Feb 10, 2018
Updated implementation to V8 version 5.9: - use `v8::Local` instead of `v8::Handle` - use `v8::Global` instead of `v8::PersistentHandle` - use functions returning `MaybeLocal` Updated V8 versions in Travis script and Makefile, switched to `xenial` image (although it hasn't been officially released yet) Related to #50 and #66
pmed
added a commit
that referenced
this issue
Feb 10, 2018
Updated implementation to V8 version 5.9: - use `v8::Local` instead of `v8::Handle` - use `v8::Global` instead of `v8::PersistentHandle` - use functions returning `MaybeLocal` Updated V8 versions in Travis script and Makefile, switched to `xenial` image (although it hasn't been officially released yet) Related to #50 and #66
pmed
added a commit
that referenced
this issue
Feb 10, 2018
Updated implementation to V8 version 5.9: - use `v8::Local` instead of `v8::Handle` - use `v8::Global` instead of `v8::PersistentHandle` - use functions returning `MaybeLocal` Updated tests and examples. Updated V8 versions in Travis script and Makefile, switched to `xenial` image (although it hasn't been officially released yet) Related to #50 and #66
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
v8::Object::ForceSet
with isolate as first argument has been removed in v8 6.1.It looks like
v8::Object::CreateDataProperty
should be used in today's API. It looks like this is available since 4.5.Before preparing a pull request, I'd like to ask what is the strategy with regards of the v8 API level. From the point of view of C++ applications using v8, I think it makes sense that actual version of v8pp targets recent versions of v8. If someone chooses not to update v8, he probably doesn't need to update v8pp either.
For node plugins the situation might look different (I don't know that part). It looks like the oldest supported LTS is 4 and node 4.8.7 seems to run v8 version 4.5. So it looks like it is time to use API's like
CreateDataProperty
(and other changes like usingv8::Local
instead ofv8::Handle
). Would pull requests breaking support of v8 before 4.5 be accepted?The text was updated successfully, but these errors were encountered: