diff options
| author | gdamore <gdamore@users.noreply.github.com> | 2025-01-01 00:43:40 +0000 |
|---|---|---|
| committer | gdamore <gdamore@users.noreply.github.com> | 2025-01-01 00:43:40 +0000 |
| commit | 3aba32ecd7c1f14675d401f3980d7669bd61b908 (patch) | |
| tree | 275ab418c1b7cc250fef131f01d9ceabf019341c /ref/api/memory.html | |
| parent | 0ea2fdfcab92d273f4db8bd4d24bb2639763155c (diff) | |
| download | nng-3aba32ecd7c1f14675d401f3980d7669bd61b908.tar.gz nng-3aba32ecd7c1f14675d401f3980d7669bd61b908.tar.bz2 nng-3aba32ecd7c1f14675d401f3980d7669bd61b908.zip | |
deploy: b7736d01265c6d6ce4fcc6822ea3cd5e23fb7094
Diffstat (limited to 'ref/api/memory.html')
| -rw-r--r-- | ref/api/memory.html | 2 |
1 files changed, 1 insertions, 1 deletions
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 <code>malloc</co <p>If memory cannot be allocated for any reason, then <code>NULL</code> will be returned. Applications that experience this should treat this like <a href="/api/errors.html#NNG_ENOMEM"><code>NNG_ENOMEM</code></a>.</p> <p>Memory returned by <code>nng_alloc</code> can be used to hold message buffers, in which -case it can be directly passed to <a href="/TODO.html"><code>nng_send</code></a> using the flag <code>NNG_FLAG_ALLOC</code>. +case it can be directly passed to <a href="/api/sock.html#nng_send"><code>nng_send</code></a> using the flag <code>NNG_FLAG_ALLOC</code>. Alternatively, it can be freed when no longer needed using <a href="/api/memory.html#deallocate-memory"><code>nng_free</code></a>.</p> <div class="mdbook-alerts mdbook-alerts-important"> <p class="mdbook-alerts-title"> |