From dc75b114b4caf2692b145b7b254e2f6cfa627831 Mon Sep 17 00:00:00 2001 From: Neels Hofmeyr Date: Sat, 9 Dec 2017 05:51:42 +0100 Subject: comment: utils: more accurately describe OSMO_STRINGIFY macro Change-Id: I7b057c026f9df90608b7cbd12481ab9e7a41d88c --- include/osmocom/core/utils.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'include/osmocom') diff --git a/include/osmocom/core/utils.h b/include/osmocom/core/utils.h index c5cc138b..0a3805df 100644 --- a/include/osmocom/core/utils.h +++ b/include/osmocom/core/utils.h @@ -15,7 +15,9 @@ #define OSMO_MAX(a, b) ((a) >= (b) ? (a) : (b)) /*! Return the minimum of two specified values */ #define OSMO_MIN(a, b) ((a) >= (b) ? (b) : (a)) -/*! Stringify the contents of a macro, e.g. a port number */ +/*! Stringify the name of a macro x, e.g. an FSM event name. + * Note: if nested within another preprocessor macro, this will + * stringify the value of x instead of its name. */ #define OSMO_STRINGIFY(x) #x /*! Make a value_string entry from an enum value name */ #define OSMO_VALUE_STRING(x) { x, #x } -- cgit v1.2.3