mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2024-11-10 03:16:17 +01:00
Merge branch 'serializ' into 'master'
docs: Standardize spelling of serializ* See merge request GNOME/glib!2090 Helps: #2399
This commit is contained in:
commit
66fe1da95a
@ -136,7 +136,7 @@ the dconf database.
|
||||
<term><option>get</option></term>
|
||||
<listitem><para>
|
||||
Gets the value of <replaceable>KEY</replaceable>.
|
||||
The value is printed out as a serialised
|
||||
The value is printed out as a serialized
|
||||
<link linkend="GVariant"><type>GVariant</type></link>.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
@ -175,7 +175,7 @@ Queries the description of valid values for <replaceable>KEY</replaceable>.
|
||||
<term><option>set</option></term>
|
||||
<listitem><para>
|
||||
Sets the value of <replaceable>KEY</replaceable> to
|
||||
<replaceable>VALUE</replaceable>. The value is specified as a serialised
|
||||
<replaceable>VALUE</replaceable>. The value is specified as a serialized
|
||||
<link linkend="GVariant"><type>GVariant</type></link>.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
@ -263,7 +263,7 @@
|
||||
<para>
|
||||
Used as a prefix for a GVariant type string (not a prefix for a format string, so <literal>&s</literal> is
|
||||
a valid format string but <literal>&@s</literal> is not).
|
||||
Denotes that a C pointer to serialised data
|
||||
Denotes that a C pointer to serialized data
|
||||
should be used in place of the normal C type. See
|
||||
<link linkend='gvariant-format-strings-pointers'>Pointers</link> below.
|
||||
</para>
|
||||
@ -946,7 +946,7 @@ data = g_variant_new_parsed ("(%o, {'brightness': {'value': <%i>, 'max': <%i>}})
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The '<code>&</code>' character is used to indicate that serialised data should be directly exchanged via a
|
||||
The '<code>&</code>' character is used to indicate that serialized data should be directly exchanged via a
|
||||
pointer.
|
||||
</para>
|
||||
<para>
|
||||
@ -954,7 +954,7 @@ data = g_variant_new_parsed ("(%o, {'brightness': {'value': <%i>, 'max': <%i>}})
|
||||
'<literal>&o</literal>' or '<code>&g</code>'). For
|
||||
<link linkend='g-variant-new'><function>g_variant_new()</function></link> this has absolutely no effect. The string
|
||||
is collected and duplicated normally. For <link linkend='g-variant-get'><function>g_variant_get()</function></link>
|
||||
it means that instead of creating a newly allocated copy of the string, a pointer to the serialised data is
|
||||
it means that instead of creating a newly allocated copy of the string, a pointer to the serialized data is
|
||||
returned. This pointer should not be freed. Validity checks are performed to ensure that the string data will
|
||||
always be properly nul-terminated.
|
||||
</para>
|
||||
|
Loading…
Reference in New Issue
Block a user