summaryrefslogtreecommitdiffstats
path: root/lib/nexthop.c
diff options
context:
space:
mode:
authorDavid Lamparter <equinox@diac24.net>2021-02-21 06:18:10 +0100
committerDavid Lamparter <equinox@diac24.net>2021-03-17 06:18:17 +0100
commitbf8d3d6aca3f20255a621ed1c148fd05b3a8ae5c (patch)
treecd62a7c64fe8eb9f3252e1b608f1fb939c2a772c /lib/nexthop.c
parent*: require ISO C11 (or C++11) (diff)
downloadfrr-bf8d3d6aca3f20255a621ed1c148fd05b3a8ae5c.tar.xz
frr-bf8d3d6aca3f20255a621ed1c148fd05b3a8ae5c.zip
*: require semicolon after DEFINE_MTYPE & co
Back when I put this together in 2015, ISO C11 was still reasonably new and we couldn't require it just yet. Without ISO C11, there is no "good" way (only bad hacks) to require a semicolon after a macro that ends with a function definition. And if you added one anyway, you'd get "spurious semicolon" warnings on some compilers... With C11, `_Static_assert()` at the end of a macro will make it so that the semicolon is properly required, consumed, and not warned about. Consistently requiring semicolons after "file-level" macros matches Linux kernel coding style and helps some editors against mis-syntax'ing these macros. Signed-off-by: David Lamparter <equinox@diac24.net>
Diffstat (limited to 'lib/nexthop.c')
-rw-r--r--lib/nexthop.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/nexthop.c b/lib/nexthop.c
index dd8c10820..17ef95c68 100644
--- a/lib/nexthop.c
+++ b/lib/nexthop.c
@@ -34,8 +34,8 @@
#include "vrf.h"
#include "nexthop_group.h"
-DEFINE_MTYPE_STATIC(LIB, NEXTHOP, "Nexthop")
-DEFINE_MTYPE_STATIC(LIB, NH_LABEL, "Nexthop label")
+DEFINE_MTYPE_STATIC(LIB, NEXTHOP, "Nexthop");
+DEFINE_MTYPE_STATIC(LIB, NH_LABEL, "Nexthop label");
static int _nexthop_labels_cmp(const struct nexthop *nh1,
const struct nexthop *nh2)