-
-
Notifications
You must be signed in to change notification settings - Fork 517
Signature::New signature changed in V8 4.2 #308
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
Are there any serious users? If there aren't, it's probably easier to remove it. |
It was removed in this issue. Easiest way does seem like removing the option of setting arguments for signatures. I don't think it's worth it to reimplement a |
Change https://github.com/rvagg/nan/blob/master/nan_new.h#L153 to Factory<v8::Signature>::return_t
Factory<v8::Signature>::New( Factory<v8::Signature>::FTH receiver) {
return v8::Signature::New(v8::Isolate::GetCurrent(), receiver);
} Change https://github.com/rvagg/nan/blob/master/nan_implementation_pre_12_inl.h#183-188 to Factory<v8::Signature>::return_t
Factory<v8::Signature>::New( Factory<v8::Signature>::FTH receiver) {
return v8::Signature::New(receiver);
} |
I'm not sure how to tackle this one cause the
NanNew
stuff has changed quite a bit since I touched it and the split across multiple files has me scratching myself.I'm trying out io.js next which has V8 4.2.77 and am bumping in to compile problems related to the new signature of this method:
Not super-urgent but we only have a couple of weeks before this goes live.
The text was updated successfully, but these errors were encountered: