From edd3b6bc34f211bd3d58642d0c69ce1b5bb9dc3b Mon Sep 17 00:00:00 2001 From: gdamore Date: Thu, 9 Oct 2025 01:22:20 +0000 Subject: deploy: 9c834956456924df7c885ab8b79573721acaff5c --- ref/api/init.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'ref/api/init.html') diff --git a/ref/api/init.html b/ref/api/init.html index 777d95fb..0fe04827 100644 --- a/ref/api/init.html +++ b/ref/api/init.html @@ -263,12 +263,12 @@ extern nng_err nng_init(nng_init_params *params);

Before using other interfaces in this library, it is necessary to initialize the library. The nng_init function performs this initialization.

The function is idempotent, although on tear down, every call to nng_init must -be paired with a call to nng_fini or no resources will be released. +be paired with a call to nng_fini or no resources will be released. This allows for libraries consuming these interfaces to safely initialize and finalize the library without disrupting other consumers in the same process.

Further, only the first call to this function may have a value of params other than NULL. If params is not NULL, and the library has already been intiazed, then nng_init will -return NNG_EBUSY.

+return NNG_EBUSY.

In some cases it is desirable to tune certain runtime parameters for the library, which can be done by supplying a non-NULL params argument.

Parameters

@@ -312,7 +312,7 @@ Changes the number of threads used for asynchronous DNS look ups.

When the consumer is ready to deallocate any resources allocated by the library, it should call the nng_fini function. Each call to nng_fini should be paired with an earlier call to -nng_init.

+nng_init.

After calling nng_fini, the consuming application must not make any other calls to NNG functions, except that it may use nng_init to initialize the application for further use.