On 07.08.2018 00:30, Paul Goyette wrote:
While looking at some other stuff, I noticed that the operations
described in bitstring(3) and implement as macros in include/bitstring.h
can have a multiple-evaluation problem if the macro arguments have side
effects (such as a ++ on the bit-number).
Shouldn't we include a warning about this, both in the man page and in
the code?
It looks like the calls with multiple evaluations could be changed into
static inline functions wrapped with a macro, analogously to EV_SET from
<sys/event.h>.