Skip to content
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.

chakrashim: fix for nan compatibility #93

Merged
merged 1 commit into from
Jul 13, 2016

Conversation

kunalspathak
Copy link
Member

Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

chakrashim

Description of change

nan was failing to build because of change in signature. Fixed it and deprecated old API.
Fixes: #90


Local<Value> BooleanObject::New(bool value) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder we should still keep deprecated implementation, in case anybody using deprecated API? It can be removed when the declaration is removed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, i was debating that myself if i should keep it or remove it. AFAIK, no one can use the deprecated because it will fail the build of that module because of V8_DEPRECATED macro, right? But checking v8's code, they have kept it so would be ok to just leave it instead of deleting.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe using deprecated APIs only result in a build warning by default, not failure?

@jianchun
Copy link

jianchun commented Jul 7, 2016

👍 Thanks!

PR-URL: nodejs#93
Reviewed-By: Jianchun Xu <Jianchun.Xu@microsoft.com>
Fixes: nodejs#90
@kunalspathak kunalspathak merged commit 21bd447 into nodejs:chakracore-master Jul 13, 2016
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.

2 participants