From 3aba32ecd7c1f14675d401f3980d7669bd61b908 Mon Sep 17 00:00:00 2001 From: gdamore Date: Wed, 1 Jan 2025 00:43:40 +0000 Subject: deploy: b7736d01265c6d6ce4fcc6822ea3cd5e23fb7094 --- ref/api/memory.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'ref/api/memory.html') diff --git a/ref/api/memory.html b/ref/api/memory.html index 7e5a7e8d..9fa8b5bd 100644 --- a/ref/api/memory.html +++ b/ref/api/memory.html @@ -235,7 +235,7 @@ Note that the memory may have random data in it, just like with mallocIf memory cannot be allocated for any reason, then NULL will be returned. Applications that experience this should treat this like NNG_ENOMEM.

Memory returned by nng_alloc can be used to hold message buffers, in which -case it can be directly passed to nng_send using the flag NNG_FLAG_ALLOC. +case it can be directly passed to nng_send using the flag NNG_FLAG_ALLOC. Alternatively, it can be freed when no longer needed using nng_free.

-- cgit v1.2.3-70-g09d2