nng_setopt_ptr MIA #285
Comments
|
This was just missing in the header file... the backing implementation was there. |
nonnenmacher
added a commit
to nonnenmacher/nng
that referenced
this issue
Mar 19, 2018
Bump API to 0.7.0. Remove .version file -- we use git tags. fixes nanomsg#293 nng_listener_getopt doc needs updating fixes nanomsg#295 boolean options should use C99 bool type fixes nanomsg#275 nng_pipe_getopt_ptr() missing? fixes nanomsg#285 nng_setopt_ptr MIS fixes nanomsg#297 nng_listener/dialer_close does not validate mode Minor markup fixes. fixes nanomsg#294 rename nng_zerotier_xxx to nng_zt_xxx fixes nanomsg#287 remove NNG_OPT_DOMAIN, NNG_OPT_PROTOCOL, and NNG_OPT_TRANSPORT Fixes for new doc layout. fixes nanomsg#286 nng_pair0_open (and all others) need man page fixes nanomsg#279 consider restructuring man sections
JaylinYu
added a commit
to nanomq/nng
that referenced
this issue
Jan 30, 2022
…ve timer in transport layer
JaylinYu
added a commit
to nanomq/nng
that referenced
this issue
Feb 3, 2022
…ve timer in transport layer
JaylinYu
added a commit
to nanomq/nng
that referenced
this issue
Apr 10, 2022
…ve timer in transport layer
muryliang
pushed a commit
to muryliang/nng
that referenced
this issue
Mar 30, 2023
…so Fix for leaking connections when calling dialer.Close() and not socket.Close() (nanomsg#285)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Noticed this while writing nng_setopt(3) man page.
We have an option to get a pointer value for a socket, but not one to pass such a thing.
We should fix that.
The text was updated successfully, but these errors were encountered: