From: Ryan Lortie Date: Fri, 21 Oct 2011 19:00:24 +0000 (-0400) Subject: GVariant format string docs: fix maybe types X-Git-Tag: 2.31.2~179 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3d13ee1b5ff2a2ad5f32704cc5f071167a8852a6;p=platform%2Fupstream%2Fglib.git GVariant format string docs: fix maybe types The documentation for maybe types failed to mention 'a' as one of the types that was handled with a single pointer for which NULL means "nothing". Correct that omission. Problem caught by Shaun McCance. --- diff --git a/docs/reference/glib/gvariant-varargs.xml b/docs/reference/glib/gvariant-varargs.xml index 1b15156..9b95f87 100644 --- a/docs/reference/glib/gvariant-varargs.xml +++ b/docs/reference/glib/gvariant-varargs.xml @@ -671,11 +671,12 @@ g_variant_unref (value);]]> - The first way is used with format strings starting with 's', 'o', - 'g', 'v', '@', '*', - '?', 'r', '&', or '^'. In all of - these cases, for non-maybe types, g_variant_new() takes - a pointer to a non-NULL value and + The first way is used with format strings starting with 'a', 's', + 'o', 'g', 'v', '@', + '*', '?', 'r', '&', or + '^'. In all of these cases, for non-maybe types, + g_variant_new() takes a pointer to a + non-NULL value and g_variant_get() returns (by reference) a non-NULL pointer. When any of these format strings are prefixed with an 'm', the type of arguments that are collected does not change in any way, but