koffi 0.9.4 → 0.9.5

package/vendor/node-addon-api/doc/array_buffer.md

@@ -1,155 +1,155 @@
-# ArrayBuffer
-
-Class `Napi::ArrayBuffer` inherits from class [`Napi::Object`][].
-
-The `Napi::ArrayBuffer` class corresponds to the
-[JavaScript `ArrayBuffer`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer)
-class.
-
-## Methods
-
-### New
-
-Allocates a new `Napi::ArrayBuffer` instance with a given length.
-
-```cpp
-static Napi::ArrayBuffer Napi::ArrayBuffer::New(napi_env env, size_t byteLength);
-```
-
-- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
-- `[in] byteLength`: The length to be allocated, in bytes.
-
-Returns a new `Napi::ArrayBuffer` instance.
-
-### New
-
-Wraps the provided external data into a new `Napi::ArrayBuffer` instance.
-
-The `Napi::ArrayBuffer` instance does not assume ownership for the data and
-expects it to be valid for the lifetime of the instance. Since the
-`Napi::ArrayBuffer` is subject to garbage collection this overload is only
-suitable for data which is static and never needs to be freed.
-This factory method will not provide the caller with an opportunity to free the
-data when the `Napi::ArrayBuffer` gets garbage-collected. If you need to free
-the data retained by the `Napi::ArrayBuffer` object please use other
-variants of the `Napi::ArrayBuffer::New` factory method that accept
-`Napi::Finalizer`, which is a function that will be invoked when the
-`Napi::ArrayBuffer` object has been destroyed.
-
-```cpp
-static Napi::ArrayBuffer Napi::ArrayBuffer::New(napi_env env, void* externalData, size_t byteLength);
-```
-
-- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
-- `[in] externalData`: The pointer to the external data to wrap.
-- `[in] byteLength`: The length of the `externalData`, in bytes.
-
-Returns a new `Napi::ArrayBuffer` instance.
-
-### New
-
-Wraps the provided external data into a new `Napi::ArrayBuffer` instance.
-
-The `Napi::ArrayBuffer` instance does not assume ownership for the data and
-expects it to be valid for the lifetime of the instance. The data can only be
-freed once the `finalizeCallback` is invoked to indicate that the
-`Napi::ArrayBuffer` has been released.
-
-```cpp
-template <typename Finalizer>
-static Napi::ArrayBuffer Napi::ArrayBuffer::New(napi_env env,
-                       void* externalData,
-                       size_t byteLength,
-                       Finalizer finalizeCallback);
-```
-
-- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
-- `[in] externalData`: The pointer to the external data to wrap.
-- `[in] byteLength`: The length of the `externalData`, in bytes.
-- `[in] finalizeCallback`: A function to be called when the `Napi::ArrayBuffer` is
-  destroyed. It must implement `operator()`, accept a `void*` (which is the
-  `externalData` pointer), and return `void`.
-
-Returns a new `Napi::ArrayBuffer` instance.
-
-### New
-
-Wraps the provided external data into a new `Napi::ArrayBuffer` instance.
-
-The `Napi::ArrayBuffer` instance does not assume ownership for the data and expects it
-to be valid for the lifetime of the instance. The data can only be freed once
-the `finalizeCallback` is invoked to indicate that the `Napi::ArrayBuffer` has been
-released.
-
-```cpp
-template <typename Finalizer, typename Hint>
-static Napi::ArrayBuffer Napi::ArrayBuffer::New(napi_env env,
-                       void* externalData,
-                       size_t byteLength,
-                       Finalizer finalizeCallback,
-                       Hint* finalizeHint);
-```
-
-- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
-- `[in] externalData`: The pointer to the external data to wrap.
-- `[in] byteLength`: The length of the `externalData`, in bytes.
-- `[in] finalizeCallback`: The function to be called when the `Napi::ArrayBuffer` is
-  destroyed. It must implement `operator()`, accept a `void*` (which is the
-  `externalData` pointer) and `Hint*`, and return `void`.
-- `[in] finalizeHint`: The hint to be passed as the second parameter of the
-  finalize callback.
-
-Returns a new `Napi::ArrayBuffer` instance.
-
-### Constructor
-
-Initializes an empty instance of the `Napi::ArrayBuffer` class.
-
-```cpp
-Napi::ArrayBuffer::ArrayBuffer();
-```
-
-### Constructor
-
-Initializes a wrapper instance of an existing `Napi::ArrayBuffer` object.
-
-```cpp
-Napi::ArrayBuffer::ArrayBuffer(napi_env env, napi_value value);
-```
-
-- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
-- `[in] value`: The `Napi::ArrayBuffer` reference to wrap.
-
-### ByteLength
-
-```cpp
-size_t Napi::ArrayBuffer::ByteLength() const;
-```
-
-Returns the length of the wrapped data, in bytes.
-
-### Data
-
-```cpp
-void* Napi::ArrayBuffer::Data() const;
-```
-
-Returns a pointer the wrapped data.
-
-### Detach
-
-```cpp
-void Napi::ArrayBuffer::Detach();
-```
-
-Invokes the `ArrayBuffer` detach operation on a detachable `ArrayBuffer`.
-
-### IsDetached
-
-```cpp
-bool Napi::ArrayBuffer::IsDetached() const;
-```
-
-Returns `true` if this `ArrayBuffer` has been detached.
-
-[`Napi::Object`]: ./object.md
+# ArrayBuffer
+
+Class `Napi::ArrayBuffer` inherits from class [`Napi::Object`][].
+
+The `Napi::ArrayBuffer` class corresponds to the
+[JavaScript `ArrayBuffer`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer)
+class.
+
+## Methods
+
+### New
+
+Allocates a new `Napi::ArrayBuffer` instance with a given length.
+
+```cpp
+static Napi::ArrayBuffer Napi::ArrayBuffer::New(napi_env env, size_t byteLength);
+```
+
+- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
+- `[in] byteLength`: The length to be allocated, in bytes.
+
+Returns a new `Napi::ArrayBuffer` instance.
+
+### New
+
+Wraps the provided external data into a new `Napi::ArrayBuffer` instance.
+
+The `Napi::ArrayBuffer` instance does not assume ownership for the data and
+expects it to be valid for the lifetime of the instance. Since the
+`Napi::ArrayBuffer` is subject to garbage collection this overload is only
+suitable for data which is static and never needs to be freed.
+This factory method will not provide the caller with an opportunity to free the
+data when the `Napi::ArrayBuffer` gets garbage-collected. If you need to free
+the data retained by the `Napi::ArrayBuffer` object please use other
+variants of the `Napi::ArrayBuffer::New` factory method that accept
+`Napi::Finalizer`, which is a function that will be invoked when the
+`Napi::ArrayBuffer` object has been destroyed.
+
+```cpp
+static Napi::ArrayBuffer Napi::ArrayBuffer::New(napi_env env, void* externalData, size_t byteLength);
+```
+
+- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
+- `[in] externalData`: The pointer to the external data to wrap.
+- `[in] byteLength`: The length of the `externalData`, in bytes.
+
+Returns a new `Napi::ArrayBuffer` instance.
+
+### New
+
+Wraps the provided external data into a new `Napi::ArrayBuffer` instance.
+
+The `Napi::ArrayBuffer` instance does not assume ownership for the data and
+expects it to be valid for the lifetime of the instance. The data can only be
+freed once the `finalizeCallback` is invoked to indicate that the
+`Napi::ArrayBuffer` has been released.
+
+```cpp
+template <typename Finalizer>
+static Napi::ArrayBuffer Napi::ArrayBuffer::New(napi_env env,
+                       void* externalData,
+                       size_t byteLength,
+                       Finalizer finalizeCallback);
+```
+
+- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
+- `[in] externalData`: The pointer to the external data to wrap.
+- `[in] byteLength`: The length of the `externalData`, in bytes.
+- `[in] finalizeCallback`: A function to be called when the `Napi::ArrayBuffer` is
+  destroyed. It must implement `operator()`, accept a `void*` (which is the
+  `externalData` pointer), and return `void`.
+
+Returns a new `Napi::ArrayBuffer` instance.
+
+### New
+
+Wraps the provided external data into a new `Napi::ArrayBuffer` instance.
+
+The `Napi::ArrayBuffer` instance does not assume ownership for the data and expects it
+to be valid for the lifetime of the instance. The data can only be freed once
+the `finalizeCallback` is invoked to indicate that the `Napi::ArrayBuffer` has been
+released.
+
+```cpp
+template <typename Finalizer, typename Hint>
+static Napi::ArrayBuffer Napi::ArrayBuffer::New(napi_env env,
+                       void* externalData,
+                       size_t byteLength,
+                       Finalizer finalizeCallback,
+                       Hint* finalizeHint);
+```
+
+- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
+- `[in] externalData`: The pointer to the external data to wrap.
+- `[in] byteLength`: The length of the `externalData`, in bytes.
+- `[in] finalizeCallback`: The function to be called when the `Napi::ArrayBuffer` is
+  destroyed. It must implement `operator()`, accept a `void*` (which is the
+  `externalData` pointer) and `Hint*`, and return `void`.
+- `[in] finalizeHint`: The hint to be passed as the second parameter of the
+  finalize callback.
+
+Returns a new `Napi::ArrayBuffer` instance.
+
+### Constructor
+
+Initializes an empty instance of the `Napi::ArrayBuffer` class.
+
+```cpp
+Napi::ArrayBuffer::ArrayBuffer();
+```
+
+### Constructor
+
+Initializes a wrapper instance of an existing `Napi::ArrayBuffer` object.
+
+```cpp
+Napi::ArrayBuffer::ArrayBuffer(napi_env env, napi_value value);
+```
+
+- `[in] env`: The environment in which to create the `Napi::ArrayBuffer` instance.
+- `[in] value`: The `Napi::ArrayBuffer` reference to wrap.
+
+### ByteLength
+
+```cpp
+size_t Napi::ArrayBuffer::ByteLength() const;
+```
+
+Returns the length of the wrapped data, in bytes.
+
+### Data
+
+```cpp
+void* Napi::ArrayBuffer::Data() const;
+```
+
+Returns a pointer the wrapped data.
+
+### Detach
+
+```cpp
+void Napi::ArrayBuffer::Detach();
+```
+
+Invokes the `ArrayBuffer` detach operation on a detachable `ArrayBuffer`.
+
+### IsDetached
+
+```cpp
+bool Napi::ArrayBuffer::IsDetached() const;
+```
+
+Returns `true` if this `ArrayBuffer` has been detached.
+
+[`Napi::Object`]: ./object.md

package/vendor/node-addon-api/doc/async_context.md

@@ -1,86 +1,86 @@
-# AsyncContext
-
-The [Napi::AsyncWorker](async_worker.md) class may not be appropriate for every
-scenario. When using any other async mechanism, introducing a new class
-`Napi::AsyncContext` is necessary to ensure an async operation is properly
-tracked by the runtime. The `Napi::AsyncContext` class can be passed to
-[Napi::Function::MakeCallback()](function.md) method to properly restore the
-correct async execution context.
-
-## Methods
-
-### Constructor
-
-Creates a new `Napi::AsyncContext`.
-
-```cpp
-explicit Napi::AsyncContext::AsyncContext(napi_env env, const char* resource_name);
-```
-
-- `[in] env`: The environment in which to create the `Napi::AsyncContext`.
-- `[in] resource_name`: Null-terminated strings that represents the
-identifier for the kind of resource that is being provided for diagnostic
-information exposed by the `async_hooks` API.
-
-### Constructor
-
-Creates a new `Napi::AsyncContext`.
-
-```cpp
-explicit Napi::AsyncContext::AsyncContext(napi_env env, const char* resource_name, const Napi::Object& resource);
-```
-
-- `[in] env`: The environment in which to create the `Napi::AsyncContext`.
-- `[in] resource_name`: Null-terminated strings that represents the
-identifier for the kind of resource that is being provided for diagnostic
-information exposed by the `async_hooks` API.
-- `[in] resource`: Object associated with the asynchronous operation that
-will be passed to possible `async_hooks`.
-
-### Destructor
-
-The `Napi::AsyncContext` to be destroyed.
-
-```cpp
-virtual Napi::AsyncContext::~AsyncContext();
-```
-
-### Env
-
-Requests the environment in which the async context has been initially created.
-
-```cpp
-Napi::Env Env() const;
-```
-
-Returns the `Napi::Env` environment in which the async context has been created.
-
-## Operator
-
-```cpp
-Napi::AsyncContext::operator napi_async_context() const;
-```
-
-Returns the Node-API `napi_async_context` wrapped by the `Napi::AsyncContext`
-object. This can be used to mix usage of the C Node-API and node-addon-api.
-
-## Example
-
-```cpp
-#include "napi.h"
-
-void MakeCallbackWithAsyncContext(const Napi::CallbackInfo& info) {
-  Napi::Function callback = info[0].As<Napi::Function>();
-  Napi::Object resource = info[1].As<Napi::Object>();
-
-  // Create a new async context instance.
-  Napi::AsyncContext context(info.Env(), "async_context_test", resource);
-
-  // Invoke the callback with the async context instance.
-  callback.MakeCallback(Napi::Object::New(info.Env()),
-      std::initializer_list<napi_value>{}, context);
-
-  // The async context instance is automatically destroyed here because it's
-  // block-scope like `Napi::HandleScope`.
-}
-```
+# AsyncContext
+
+The [Napi::AsyncWorker](async_worker.md) class may not be appropriate for every
+scenario. When using any other async mechanism, introducing a new class
+`Napi::AsyncContext` is necessary to ensure an async operation is properly
+tracked by the runtime. The `Napi::AsyncContext` class can be passed to
+[Napi::Function::MakeCallback()](function.md) method to properly restore the
+correct async execution context.
+
+## Methods
+
+### Constructor
+
+Creates a new `Napi::AsyncContext`.
+
+```cpp
+explicit Napi::AsyncContext::AsyncContext(napi_env env, const char* resource_name);
+```
+
+- `[in] env`: The environment in which to create the `Napi::AsyncContext`.
+- `[in] resource_name`: Null-terminated strings that represents the
+identifier for the kind of resource that is being provided for diagnostic
+information exposed by the `async_hooks` API.
+
+### Constructor
+
+Creates a new `Napi::AsyncContext`.
+
+```cpp
+explicit Napi::AsyncContext::AsyncContext(napi_env env, const char* resource_name, const Napi::Object& resource);
+```
+
+- `[in] env`: The environment in which to create the `Napi::AsyncContext`.
+- `[in] resource_name`: Null-terminated strings that represents the
+identifier for the kind of resource that is being provided for diagnostic
+information exposed by the `async_hooks` API.
+- `[in] resource`: Object associated with the asynchronous operation that
+will be passed to possible `async_hooks`.
+
+### Destructor
+
+The `Napi::AsyncContext` to be destroyed.
+
+```cpp
+virtual Napi::AsyncContext::~AsyncContext();
+```
+
+### Env
+
+Requests the environment in which the async context has been initially created.
+
+```cpp
+Napi::Env Env() const;
+```
+
+Returns the `Napi::Env` environment in which the async context has been created.
+
+## Operator
+
+```cpp
+Napi::AsyncContext::operator napi_async_context() const;
+```
+
+Returns the Node-API `napi_async_context` wrapped by the `Napi::AsyncContext`
+object. This can be used to mix usage of the C Node-API and node-addon-api.
+
+## Example
+
+```cpp
+#include "napi.h"
+
+void MakeCallbackWithAsyncContext(const Napi::CallbackInfo& info) {
+  Napi::Function callback = info[0].As<Napi::Function>();
+  Napi::Object resource = info[1].As<Napi::Object>();
+
+  // Create a new async context instance.
+  Napi::AsyncContext context(info.Env(), "async_context_test", resource);
+
+  // Invoke the callback with the async context instance.
+  callback.MakeCallback(Napi::Object::New(info.Env()),
+      std::initializer_list<napi_value>{}, context);
+
+  // The async context instance is automatically destroyed here because it's
+  // block-scope like `Napi::HandleScope`.
+}
+```

package/vendor/node-addon-api/doc/async_operations.md

@@ -1,31 +1,31 @@
-# Asynchronous operations
-
-Node.js native add-ons often need to execute long running tasks and to avoid
-blocking the **event loop** they have to run them asynchronously from the
-**event loop**.
-In the Node.js model of execution the event loop thread represents the thread
-where JavaScript code is executing. The Node.js guidance is to avoid blocking
-other work queued on the event loop thread. Therefore, we need to do this work on
-another thread.
-
-All this means that native add-ons need to leverage async helpers from libuv as
-part of their implementation. This allows them to schedule work to be executed
-asynchronously so that their methods can return in advance of the work being
-completed.
-
-Node Addon API provides an interface to support functions that cover
-the most common asynchronous use cases. There is an abstract classes to implement
-asynchronous operations:
-
-- **[`Napi::AsyncWorker`](async_worker.md)**
-
-These class helps manage asynchronous operations through an abstraction
-of the concept of moving data between the **event loop** and **worker threads**.
-
-Also, the above class may not be appropriate for every scenario. When using any
-other asynchronous mechanism, the following API is necessary to ensure an
-asynchronous operation is properly tracked by the runtime:
-
-- **[AsyncContext](async_context.md)**
-
-- **[CallbackScope](callback_scope.md)**
+# Asynchronous operations
+
+Node.js native add-ons often need to execute long running tasks and to avoid
+blocking the **event loop** they have to run them asynchronously from the
+**event loop**.
+In the Node.js model of execution the event loop thread represents the thread
+where JavaScript code is executing. The Node.js guidance is to avoid blocking
+other work queued on the event loop thread. Therefore, we need to do this work on
+another thread.
+
+All this means that native add-ons need to leverage async helpers from libuv as
+part of their implementation. This allows them to schedule work to be executed
+asynchronously so that their methods can return in advance of the work being
+completed.
+
+Node Addon API provides an interface to support functions that cover
+the most common asynchronous use cases. There is an abstract classes to implement
+asynchronous operations:
+
+- **[`Napi::AsyncWorker`](async_worker.md)**
+
+These class helps manage asynchronous operations through an abstraction
+of the concept of moving data between the **event loop** and **worker threads**.
+
+Also, the above class may not be appropriate for every scenario. When using any
+other asynchronous mechanism, the following API is necessary to ensure an
+asynchronous operation is properly tracked by the runtime:
+
+- **[AsyncContext](async_context.md)**
+
+- **[CallbackScope](callback_scope.md)**