ref.c: do not change ref count when release function is not set
authorPhilippe Proulx <eeppeliteloop@gmail.com>
Wed, 24 May 2017 22:17:25 +0000 (18:17 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Sun, 28 May 2017 16:57:44 +0000 (12:57 -0400)
commitb1912a652c31a5700b07500b0b1dab274d06ea17
treee98dcc13a53a046228f5b2f63a6dabadb3f074d5
parentc2db73d1b0ef9e63a6a4dac2ce5ca3f3f00fcfb7
ref.c: do not change ref count when release function is not set

This is the case of the null value singleton, bt_value_null, on which
you can call bt_get() and bt_put() and they should have no effect.
Before this patch, we can see log messages of the ref count going from 0
to 18446744073709551615 and other weird, huge values.

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
lib/ref.c
This page took 0.025984 seconds and 4 git commands to generate.