-
Notifications
You must be signed in to change notification settings - Fork 30k
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
src: export the ParseEncoding function on Windows #1596
Conversation
cc @indutny / @bnoordhuis |
enum encoding ParseEncoding(v8::Isolate* isolate, | ||
v8::Handle<v8::Value> encoding_v, | ||
enum encoding default_encoding = BINARY); | ||
NODE_EXTERN enum encoding ParseEncoding(v8::Isolate* isolate, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please move v8::Isolate*
and friends on a next line at 4 space indent. No need to cascade things ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, fixed
Generally, LGTM. Is there anything else that needs exporting? |
Makes the ParseEncoding symbol visible to addons on Windows. It was already visible on Unices.
Not that I know about, in |
Ok, @Fishrock123 could you please land this? |
@ivan btw, thank you for fixing this! ;) |
@indutny Yep, will do. |
Makes the ParseEncoding symbol visible to addons on Windows. It was already visible on Unices. PR-URL: #1596 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Thanks, landed in c43855c |
Makes the ParseEncoding symbol visible to addons on Windows. It was already visible on Unices. PR-URL: nodejs#1596 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Makes the
ParseEncoding
symbol visible to addons on Windows. It was already visible on Unices.I ran into this when writing an addon that used
ParseEncoding
; the VS2013 build failed with:It built fine after adding the
NODE_EXPORT
.Similar to an older fix nodejs/node-v0.x-archive#3811