Returns a pointer to the serialised form of a glib.Variant instance.
The returned data may not be in fully-normalised form if read from an
untrusted source. The returned data must not be freed; it remains
valid for as long as value exists.
If value is a fixed-sized value that was deserialised from a
corrupted serialised container then NULL may be returned. In this
case, the proper thing to do is typically to use the appropriate
number of nul bytes in place of value. If value is not fixed-sized
then NULL is never returned.
In the case that value is already in serialised form, this function
is O(1). If the value is not already in serialised form,
serialisation occurs implicitly and is approximately O(n) in the size
of the result.
To deserialise the data returned by this function, in addition to the
serialised data, you must know the type of the glib.Variant, and (if the
machine might be different) the endianness of the machine that stored
it. As a result, file formats or network messages that incorporate
serialised glib.Variants must include this information either
implicitly (for instance "the file always contains a
G_VARIANT_TYPE_VARIANT and it is always in little-endian order") or
explicitly (by storing the type and/or endianness in addition to the
serialised data).
Returns a pointer to the serialised form of a glib.Variant instance. The returned data may not be in fully-normalised form if read from an untrusted source. The returned data must not be freed; it remains valid for as long as value exists.
If value is a fixed-sized value that was deserialised from a corrupted serialised container then NULL may be returned. In this case, the proper thing to do is typically to use the appropriate number of nul bytes in place of value. If value is not fixed-sized then NULL is never returned.
In the case that value is already in serialised form, this function is O(1). If the value is not already in serialised form, serialisation occurs implicitly and is approximately O(n) in the size of the result.
To deserialise the data returned by this function, in addition to the serialised data, you must know the type of the glib.Variant, and (if the machine might be different) the endianness of the machine that stored it. As a result, file formats or network messages that incorporate serialised glib.Variants must include this information either implicitly (for instance "the file always contains a G_VARIANT_TYPE_VARIANT and it is always in little-endian order") or explicitly (by storing the type and/or endianness in addition to the serialised data).