Thomas Haller cd31437024 shared: drop _STATIC variant of macros that define functions ... Several macros are used to define function. They had a "_STATIC" variant, to define the function as static. I think those macros should not try to abstract entirely what they do. They should not accept the function scope as argument (or have two variants per scope). This also because it might make sense to add additional __attribute__(()) to the function. That only works, if the macro does not pretend to *not* define a plain function. Instead, embrace what the function does and let the users place the function scope as they see fit. This also follows what is already done with static NM_CACHED_QUARK_FCN ("autoconnect-root", autoconnect_root_quark)		2020-02-13 17:17:07 +01:00
..
meson.build	shared: move "shared/nm-utils/tests/test-shared-general" to "shared/nm-glib-aux/tests"	2019-12-10 09:17:17 +01:00
test-shared-general.c	shared: drop _STATIC variant of macros that define functions	2020-02-13 17:17:07 +01:00