These definitions were not properly protected from unwanted operator
precedence interactions.
Existing use sites in-tree all use & or |, so this does not change any
actual behaviour in-tree.
The same seems likely to be true in external callers.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
#define XBT_NULL 0
-#define XS_OPEN_READONLY 1UL<<0
-#define XS_OPEN_SOCKETONLY 1UL<<1
+#define XS_OPEN_READONLY (1UL<<0)
+#define XS_OPEN_SOCKETONLY (1UL<<1)
/*
* Setting XS_UNWATCH_FILTER arranges that after xs_unwatch, no
* xs_unwatch for the first watch
* has returned.
*/
-#define XS_UNWATCH_FILTER 1UL<<2
+#define XS_UNWATCH_FILTER (1UL<<2)
struct xs_handle;
typedef uint32_t xs_transaction_t;