External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-12 21:05:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
080ab92587
libvirt/docs/glib-adoption.rst
Ján Tomko 080ab92587 docs: glib-adoption: remove stuff we alredy removed 
https://www.redhat.com/archives/libvir-list/2020-May/msg00299.html

Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Ján Tomko <jtomko@redhat.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2020-10-02 14:10:44 +02:00

1.4 KiB
Raw Blame History

Adoption of GLib APIs

Libvirt has adopted use of the GLib library. Due to libvirt's long history of development, there are many APIs in libvirt, for which GLib provides an alternative solution. The general rule to follow is that the standard GLib solution will be preferred over historical libvirt APIs. Existing code will be ported over to use GLib APIs over time, but new code should use the GLib APIs straight away where possible.

The following is a list of libvirt APIs that should no longer be used in new code, and their suggested GLib replacements:

VIR_ALLOC, VIR_REALLOC, VIR_RESIZE_N, VIR_EXPAND_N, VIR_SHRINK_N, VIR_FREE, VIR_APPEND_ELEMENT, VIR_INSERT_ELEMENT, VIR_DELETE_ELEMENT

Prefer the GLib APIs g_new0/g_renew/ g_free in most cases. There should rarely be a need to use g_malloc/g_realloc. Instead of using plain C arrays, it is preferrable to use one of the GLib types, GArray, GPtrArray or GByteArray. These all use a struct to track the array memory and size together and efficiently resize. NEVER MIX use of the classic libvirt memory allocation APIs and GLib APIs within a single method. Keep the style consistent, converting existing code to GLib style in a separate, prior commit.