Skip to content
This repository has been archived by the owner on Dec 9, 2018. It is now read-only.

Support Atom shell's version of node and v8 #145

Closed
wants to merge 1 commit into from

Conversation

waTeim
Copy link

@waTeim waTeim commented Jan 12, 2015

This fix is to allow the use of ContextDisposedNotification across incompatible declarations by using the atom-shell's NODE_VERSION_MINOR of 13 which is different from the currently used values of 10 and 11 by Joyent and so will not conflict with other software using contextify. Fixes #144

@kkoopa
Copy link
Collaborator

kkoopa commented Jan 12, 2015

Thanks for reporting and submitting a patch. However, it would be better to also match newer versions, ensuring possible forward compatibility. Moreover, as this is a v8 compatibility issue, I'll update NAN to account for this change and then make use of the fix through that.

@waTeim
Copy link
Author

waTeim commented Jan 12, 2015

No problem. As far as new versions go, who knows? But looks like updating nah.h is better if it can sense v8 versions independent of node versions.

@kkoopa
Copy link
Collaborator

kkoopa commented Jan 12, 2015

It cannot directly sense v8 versions, but we are in the process of rolling out NAN 1.5, which will support io.js in addition to joyent/node. For this reason, we will have to add this and other stuff to NAN, accomodating new v8 versions and the fork of node.

I'll see to it that this works on both joyent/node and io.js, which should give support for new atom shell too.

On January 12, 2015 11:02:08 PM EET, Jeff Waller notifications@github.com wrote:

No problem. As far as new versions go, who knows? But looks like
updating nah.h is better if it can sense v8 versions independent of
node versions.


Reply to this email directly or view it on GitHub:
#145 (comment)

@kkoopa
Copy link
Collaborator

kkoopa commented Jan 14, 2015

This will actually not be that easy. Checking for a minor version of 13 is not reliable.Checking for NODE_MODULE_VERSION >= 17 might work, but 17 is quite low to start with -- eventually joyent/node may itself run into module version 17. io.js went ahead and started at 42. If people are going to fork stuff and make incompatible changes they should add in some unique defines so it is at least possible to detect.

@waTeim
Copy link
Author

waTeim commented Jan 14, 2015

Haha yea no kidding. But right now today there is a problem which has gotten worse as of yesterday because guess what version of v8 iojs uses? I agree that the simple check = 13 is not enough especially now (today as opposed to 2 days ago). Maybe NAN can deal with this and maybe not, but because people are going to start clamoring for something that will allow their stuff to work across lots of versions of v8 irrespective of the node version the check for node v.x ---> v8 v.y is not longer good enough, so how about today we try.

  1. as a workaround find some signature define in v8.h 3.29 -- probably is one

@kkoopa
Copy link
Collaborator

kkoopa commented Jan 14, 2015

Let's move this discussion to nodejs/nan#226. As you said, we need a reliable way of doing this. I have compiled a list of v8 changes that need addressing, ContextDisposedNotification is but one of them.

@waTeim
Copy link
Author

waTeim commented Jan 14, 2015

Yep, did so, added a comment too. getting ahold of iojs locally currently.

@brianmcd
Copy link
Owner

brianmcd commented Feb 9, 2015

I think this PR is obsolete now? Let me know if not.

@brianmcd brianmcd closed this Feb 9, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error compiling when using v8 3.29
3 participants