-
-
Notifications
You must be signed in to change notification settings - Fork 35
Tweaks to API suggested on EPS #25
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
For the third point, I think v8's string API takes int as parameters. So we should keep it consistent to v8 api. |
The first suggestion does not break the ABI, though it could break source code, if someone is implicitly converting one of those typedefs to |
And yes, items 2, 3, and 4 were resolved long ago. |
Looks like these have all been addressed long ago, closing. Please let us know if that was not the right thing to do. |
Uh oh!
There was an error while loading. Please reload this page.
Suggestions from Ben on nodejs/node-eps#20 (comment)
Using typedef'd pointers has the issue that they will silently decay to void* when used in a void* context. Can be avoided by wrapping the pointer in a struct, like so:
typedef struct napi_value { struct napi_value *v; } napi_value;
Why int instead of size_t?
The text was updated successfully, but these errors were encountered: