Searched refs:napi_instanceof (Results 1 – 5 of 5) sorted by relevance
| /third_party/node/test/js-native-api/test_general/ |
| D | test_general.c | 50 NAPI_CALL(env, napi_instanceof(env, args[0], args[1], &instanceof)); in doInstanceOf()
|
| /third_party/ejdb/src/bindings/ejdb2_node/ |
| D | js_native_api.h | 258 NAPI_EXTERN napi_status napi_instanceof(napi_env env,
|
| /third_party/node/src/ |
| D | js_native_api.h | 258 NAPI_EXTERN napi_status napi_instanceof(napi_env env,
|
| D | js_native_api_v8.cc | 2650 napi_status napi_instanceof(napi_env env, in napi_instanceof() function
|
| /third_party/node/doc/api/ |
| D | n-api.md | 720 of a certain type. This is a stronger check than [`napi_instanceof`][], because
3417 ### napi_instanceof subsection
3424 napi_status napi_instanceof(napi_env env,
4606 status = napi_instanceof(env, es_this, MyClass_constructor, &is_instance);
4617 There are occasions where `napi_instanceof()` is insufficient for ensuring that
4659 help, because `napi_instanceof()` can then be used to ensure that the instances
4662 Unfortunately, `napi_instanceof()` does not protect against prototype
4666 will pass the `napi_instanceof()` test for a query handle instance, while still
4679 of a higher fidelity than `napi_instanceof()` can provide, because such type-
6097 [`napi_instanceof`]: #n_api_napi_instanceof
|