]> git.ipfire.org Git - thirdparty/libvirt.git/commitdiff
docs: glib-adoption: add links to GLib documentation
authorJán Tomko <jtomko@redhat.com>
Thu, 24 Sep 2020 12:07:20 +0000 (14:07 +0200)
committerJán Tomko <jtomko@redhat.com>
Fri, 2 Oct 2020 12:10:44 +0000 (14:10 +0200)
Make life a bit easier for people unfamiliar with GLib.

Signed-off-by: Ján Tomko <jtomko@redhat.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
docs/glib-adoption.rst

index 4c389d7a343ebda3dc0a824d63ec3b9f50b66a00..1cf5b9cf9bc732f0cf8219005f6589a0614dd276 100644 (file)
@@ -18,6 +18,8 @@ Memory allocation
    ``VIR_ALLOC``, ``VIR_REALLOC``, ``VIR_RESIZE_N``,
    ``VIR_EXPAND_N``, ``VIR_SHRINK_N``, ``VIR_FREE``
 
+   https://developer.gnome.org/glib/stable/glib-Memory-Allocation.html
+
    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``. **NEVER MIX** use of the classic
@@ -28,6 +30,8 @@ Memory allocation
 Array operations
    ``VIR_APPEND_ELEMENT``, ``VIR_INSERT_ELEMENT``, ``VIR_DELETE_ELEMENT``
 
+   https://developer.gnome.org/glib/stable/glib-Arrays.html
+
    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