mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-25 06:00:08 +01:00
e64fdeeaf6
Glib has GValue which used for boxing value. Add NMValueType enum, which has a similar purpose, but it's much more limited. - contrary to GValue, the type must be tracked separately from the user-data. That is, the "user-data" is only a pointer of appropriate type, and the knowledge of the actual NMValueType is kept separately. This will be used to have a static list of meta-data that knows the value types, but keeping the values independent of this type information. With GValue this would not be possible. - the use case is much more limited. Just support basic integers, boolean and strings. Nothing fancy. Note that we already do something similar at muliple places. See for example NMVariantAttributeSpec and nm_utils_team_link_watcher_to_string(). These could/should instead use NMValueType. |
||
|---|---|---|
| .. | ||
| c-list | ||
| c-rbtree | ||
| c-siphash | ||
| c-stdaux | ||
| n-acd | ||
| nm-glib-aux | ||
| nm-libnm-core-aux | ||
| nm-libnm-core-intern | ||
| nm-std-aux | ||
| nm-udev-aux | ||
| nm-utils | ||
| systemd | ||
| meson.build | ||
| nm-default.h | ||
| nm-meta-setting.c | ||
| nm-meta-setting.h | ||
| nm-test-libnm-utils.h | ||
| nm-test-utils-impl.c | ||
| nm-version-macros.h.in | ||