[glibmm] Regenerate *_docs.xml files



commit 1138c235aca7fe23419eb3188cab2ce1f82ebf44
Author: Murray Cumming <murrayc murrayc com>
Date:   Wed Jul 31 10:36:41 2013 +0200

    Regenerate *_docs.xml files

 gio/src/gio_docs.xml   |  652 ++++++++++++++++++++++++++++++++++++++++++++++--
 glib/src/glib_docs.xml |  589 ++++++++++++++++++++++++++++++++++++++-----
 2 files changed, 1157 insertions(+), 84 deletions(-)
---
diff --git a/gio/src/gio_docs.xml b/gio/src/gio_docs.xml
index 100acee..0e7b84f 100644
--- a/gio/src/gio_docs.xml
+++ b/gio/src/gio_docs.xml
@@ -2962,6 +2962,17 @@ D-Bus call for this signal subscription.  This gives you more control
 over which match rules you add (but you must add them manually).
 </parameter_description>
 </parameter>
+<parameter name="G_DBUS_SIGNAL_FLAGS_MATCH_ARG0_NAMESPACE">
+<parameter_description> Match first arguments that
+contain a bus or interface name with the given namespace.
+</parameter_description>
+</parameter>
+<parameter name="G_DBUS_SIGNAL_FLAGS_MATCH_ARG0_PATH">
+<parameter_description> Match first arguments that
+contain an object path that is either equivalent to the given path,
+or one of the paths is a subpath of the other.
+</parameter_description>
+</parameter>
 </parameters>
 </enum>
 
@@ -19223,6 +19234,8 @@ Activates the action.
 the parameter type given at construction time).  If the parameter
 type was %NULL then @parameter must also be %NULL.
 
+If the @parameter GVariant is floating, it is consumed.
+
 Since: 2.28
 
 </description>
@@ -19995,6 +20008,115 @@ Since: 2.32
 <return></return>
 </function>
 
+<function name="g_action_name_is_valid">
+<description>
+Checks if @action_name is valid.
+
+ action_name is valid if it consists only of alphanumeric characters,
+plus '-' and '.'.  The empty string is not a valid action name.
+
+It is an error to call this function with a non-utf8 @action_name.
+ action_name must not be %NULL.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="action_name">
+<parameter_description> an potential action name
+</parameter_description>
+</parameter>
+</parameters>
+<return> %TRUE if @action_name is valid
+
+</return>
+</function>
+
+<function name="g_action_parse_detailed_name">
+<description>
+Parses a detailed action name into its separate name and target
+components.
+
+Detailed action names can have three formats.
+
+The first format is used to represent an action name with no target
+value and consists of just an action name containing no whitespace
+nor the characters ':', '(' or ')'.  For example: &quot;app.action&quot;.
+
+The second format is used to represent an action with a target value
+that is a non-empty string consisting only of alphanumerics, plus '-'
+and '.'.  In that case, the action name and target value are
+separated by a double colon (&quot;::&quot;).  For example:
+&quot;app.action::target&quot;.
+
+The third format is used to represent an action with any type of
+target value, including strings.  The target value follows the action
+name, surrounded in parens.  For example: &quot;app.action(42)&quot;.  The
+target value is parsed using g_variant_parse().  If a tuple-typed
+value is desired, it must be specified in the same way, resulting in
+two sets of parens, for example: &quot;app.action((1,2,3))&quot;.  A string
+target can be specified this way as well: &quot;app.action('target')&quot;.
+For strings, this third format must be used if * target value is
+empty or contains characters other than alphanumerics, '-' and '.'.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="detailed_name">
+<parameter_description> a detailed action name
+</parameter_description>
+</parameter>
+<parameter name="action_name">
+<parameter_description> the action name
+</parameter_description>
+</parameter>
+<parameter name="target_value">
+<parameter_description> the target value, or %NULL for no target
+</parameter_description>
+</parameter>
+<parameter name="error">
+<parameter_description> a pointer to a %NULL #GError, or %NULL
+</parameter_description>
+</parameter>
+</parameters>
+<return> %TRUE if successful, else %FALSE with @error set
+
+</return>
+</function>
+
+<function name="g_action_print_detailed_name">
+<description>
+Formats a detailed action name from @action_name and @target_value.
+
+It is an error to call this function with an invalid action name.
+
+This function is the opposite of
+g_action_parse_detailed_action_name().  It will produce a string that
+can be parsed back to the @action_name and @target_value by that
+function.
+
+See that function for the types of strings that will be printed by
+this function.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="action_name">
+<parameter_description> a valid action name
+</parameter_description>
+</parameter>
+<parameter name="target_value">
+<parameter_description> a #GVariant target value, or %NULL
+</parameter_description>
+</parameter>
+</parameters>
+<return> a detailed format string
+
+</return>
+</function>
+
 <function name="g_app_info_add_supports_type">
 <description>
 Adds a content type to the application information to indicate the 
@@ -21463,6 +21585,31 @@ reproduced here:
 </return>
 </function>
 
+<function name="g_application_mark_busy">
+<description>
+Increases the busy count of @application.
+
+Use this function to indicate that the application is busy, for instance
+while a long running operation is pending.
+
+The busy state will be exposed to other processes, so a session shell will
+use that information to indicate the state to the user (e.g. with a
+spinner).
+
+To cancel the busy indication, use g_application_unmark_busy().
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="application">
+<parameter_description> a #GApplication
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
 <function name="g_application_new">
 <description>
 Creates a new #GApplication instance.
@@ -21700,6 +21847,13 @@ if the use count falls to zero the application will exit immediately,
 except in the case that g_application_set_inactivity_timeout() is in
 use.
 
+This function sets the prgname (g_set_prgname()), if not already set,
+to the basename of argv[0].  Since 2.38, if %G_APPLICATION_IS_SERVICE
+is specified, the prgname is set to the application ID.  The main
+impact of this is is that the wmclass of windows created by Gtk+ will
+be set accordingly, which helps the window manager determine which
+application is showing the window.
+
 Since: 2.28
 
 </description>
@@ -21848,6 +22002,28 @@ Since: 2.28
 <return></return>
 </function>
 
+<function name="g_application_unmark_busy">
+<description>
+Decreases the busy count of @application.
+
+When the busy count reaches zero, the new state will be propagated
+to other processes.
+
+This function must only be called to cancel the effect of a previous
+call to g_application_mark_busy().
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="application">
+<parameter_description> a #GApplication
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
 <function name="g_async_initable_init_async">
 <description>
 Starts asynchronous initialization of the object implementing the
@@ -23158,6 +23334,43 @@ g_bus_unwatch_name() to stop watching the name.
 </return>
 </function>
 
+<function name="g_bytes_icon_get_bytes">
+<description>
+Gets the #GBytes associated with the given @icon.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="icon">
+<parameter_description> a #GIcon.
+</parameter_description>
+</parameter>
+</parameters>
+<return> a #GBytes, or %NULL.
+
+</return>
+</function>
+
+<function name="g_bytes_icon_new">
+<description>
+Creates a new icon for a bytes.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="bytes">
+<parameter_description> a #GBytes.
+</parameter_description>
+</parameter>
+</parameters>
+<return> a #GIcon for the given
+ bytes, or %NULL on error.
+
+</return>
+</function>
+
 <function name="g_cancellable_cancel">
 <description>
 Will set @cancellable to cancelled, and will emit the
@@ -27357,6 +27570,11 @@ name. As such, to avoid certain race conditions, users should be
 tracking the name owner of the well-known name and use that when
 processing the received signal.
 
+If one of %G_DBUS_SIGNAL_FLAGS_MATCH_ARG0_NAMESPACE or
+%G_DBUS_SIGNAL_FLAGS_MATCH_ARG0_PATH are given, @arg0 is
+interpreted as part of a namespace or path.  The first argument
+of a signal is matched against that part as specified by D-Bus.
+
 Since: 2.26
 
 </description>
@@ -29840,6 +30058,11 @@ Since: 2.26
 <description>
 Gets the name of the D-Bus interface the method was invoked on.
 
+If this method call is a property Get, Set or GetAll call that has
+been redirected to the method call handler then
+&quot;org.freedesktop.DBus.Properties&quot; will be returned.  See
+#GDBusInterfaceVTable for more information.
+
 Since: 2.26
 
 </description>
@@ -29883,6 +30106,11 @@ Since: 2.26
 <description>
 Gets information about the method call, if any.
 
+If this method invocation is a property Get, Set or GetAll call that
+has been redirected to the method call handler then %NULL will be
+returned.  See g_dbus_method_invocation_get_property_info() and
+#GDBusInterfaceVTable for more information.
+
 Since: 2.26
 
 </description>
@@ -29952,6 +30180,34 @@ Since: 2.26
 </return>
 </function>
 
+<function name="g_dbus_method_invocation_get_property_info">
+<description>
+Gets information about the property that this method call is for, if
+any.
+
+This will only be set in the case of an invocation in response to a
+property Get or Set call that has been directed to the method call
+handler for an object on account of its property_get() or
+property_set() vtable pointers being unset.
+
+See #GDBusInterfaceVTable for more information.
+
+If the call was GetAll, %NULL will be returned.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="invocation">
+<parameter_description> A #GDBusMethodInvocation
+</parameter_description>
+</parameter>
+</parameters>
+<return> a #GDBusPropertyInfo or %NULL
+
+</return>
+</function>
+
 <function name="g_dbus_method_invocation_get_sender">
 <description>
 Gets the bus name that invoked the method.
@@ -32332,6 +32588,33 @@ Since: 2.26
 <return></return>
 </function>
 
+<function name="g_desktop_app_info_get_action_name">
+<description>
+Gets the user-visible display name of the &quot;additional application
+action&quot; specified by @action_name.
+
+This corresponds to the &quot;Name&quot; key within the keyfile group for the
+action.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="info">
+<parameter_description> a #GDesktopAppInfo
+</parameter_description>
+</parameter>
+<parameter name="action_name">
+<parameter_description> the name of the action as from
+g_desktop_app_info_list_actions()
+</parameter_description>
+</parameter>
+</parameters>
+<return> the locale-specific action name
+
+</return>
+</function>
+
 <function name="g_desktop_app_info_get_boolean">
 <description>
 Looks up a boolean value in the keyfile backing @info.
@@ -32565,6 +32848,45 @@ Since: 2.26
 </return>
 </function>
 
+<function name="g_desktop_app_info_launch_action">
+<description>
+Activates the named application action.
+
+You may only call this function on action names that were
+returned from g_desktop_app_info_list_actions().
+
+Note that if the main entry of the desktop file indicates that the
+application supports startup notification, and @launch_context is
+non-%NULL, then startup notification will be used when activating the
+action (and as such, invocation of the action on the receiving side
+must signal the end of startup notification when it is completed).
+This is the expected behaviour of applications declaring additional
+actions, as per the desktop file specification.
+
+As with g_app_info_launch() there is no way to detect failures that
+occur while using this function.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="info">
+<parameter_description> a #GDesktopAppInfo
+</parameter_description>
+</parameter>
+<parameter name="action_name">
+<parameter_description> the name of the action as from
+g_desktop_app_info_list_actions()
+</parameter_description>
+</parameter>
+<parameter name="launch_context">
+<parameter_description> a #GAppLaunchContext
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
 <function name="g_desktop_app_info_launch_uris_as_manager">
 <description>
 This function performs the equivalent of g_app_info_launch_uris(),
@@ -32572,15 +32894,15 @@ but is intended primarily for operating system components that
 launch applications.  Ordinary applications should use
 g_app_info_launch_uris().
 
-In contrast to g_app_info_launch_uris(), all processes created will
-always be run directly as children as if by the UNIX fork()/exec()
-calls.
+If the application is launched via traditional UNIX fork()/exec()
+then @spawn_flags, @user_setup and @user_setup_data are used for the
+call to g_spawn_async().  Additionally, @pid_callback (with
+ pid_callback_data) will be called to inform about the PID of the
+created process.
 
-This guarantee allows additional control over the exact environment
-of the child processes, which is provided via a setup function
- user_setup, as well as the process identifier of each child process
-via @pid_callback. See g_spawn_async() for more information about the
-semantics of the @user_setup function.
+If application launching occurs via some other mechanism (eg: D-Bus
+activation) then @spawn_flags, @user_setup, @user_setup_data,
+ pid_callback and @pid_callback_data are ignored.
 
 
 </description>
@@ -32627,6 +32949,28 @@ each process.
 </return>
 </function>
 
+<function name="g_desktop_app_info_list_actions">
+<description>
+Returns the list of &quot;additional application actions&quot; supported on the
+desktop file, as per the desktop file specification.
+
+As per the specification, this is the list of actions that are
+explicitly listed in the &quot;Actions&quot; key of the [Desktop Entry] group.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="info">
+<parameter_description> a #GDesktopAppInfo
+</parameter_description>
+</parameter>
+</parameters>
+<return> a list of strings, always non-%NULL
+
+</return>
+</function>
+
 <function name="g_desktop_app_info_lookup_get_default_for_uri_scheme">
 <description>
 Gets the default application for launching applications 
@@ -34516,7 +34860,8 @@ Since: 2.34
 </parameter_description>
 </parameter>
 </parameters>
-<return></return>
+<return> %TRUE if the file was deleted. %FALSE otherwise.
+</return>
 </function>
 
 <function name="g_file_descriptor_based_get_fd">
@@ -35023,6 +35368,9 @@ Will block until the information is available. The #GFileInfo
 returned from this function will contain attributes that match the 
 attribute string that was passed when the #GFileEnumerator was created.
 
+See the documentation of #GFileEnumerator for information about the
+order of returned files.
+
 On error, returns %NULL and sets @error to the error. If the
 enumerator is at the end, %NULL will be returned and @error will
 be unset.
@@ -35054,6 +35402,9 @@ Request information for a number of files from the enumerator asynchronously.
 When all i/o for the operation is finished the @callback will be called with
 the requested information. 
 
+See the documentation of #GFileEnumerator for information about the
+order of returned files.
+
 The callback can be called with less than @num_files files in case of error
 or at the end of the enumerator. In case of a partial error the callback will
 be called with any succeeding items and no error, and on the next request the
@@ -37418,6 +37769,69 @@ was cancelled, the error %G_IO_ERROR_CANCELLED will be returned.
 </return>
 </function>
 
+<function name="g_file_make_directory_async">
+<description>
+Asynchronously creates a directory.
+
+Virtual: make_directory_async
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="file">
+<parameter_description> input #GFile
+</parameter_description>
+</parameter>
+<parameter name="io_priority">
+<parameter_description> the &lt;link linkend=&quot;io-priority&quot;&gt;I/O priority&lt;/link&gt;
+of the request
+</parameter_description>
+</parameter>
+<parameter name="cancellable">
+<parameter_description> optional #GCancellable object,
+%NULL to ignore
+</parameter_description>
+</parameter>
+<parameter name="callback">
+<parameter_description> a #GAsyncReadyCallback to call
+when the request is satisfied
+</parameter_description>
+</parameter>
+<parameter name="user_data">
+<parameter_description> the data to pass to callback function
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
+<function name="g_file_make_directory_finish">
+<description>
+Finishes an asynchronous directory creation, started with
+g_file_make_directory_async().
+
+Virtual: make_directory_finish
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="file">
+<parameter_description> input #GFile
+</parameter_description>
+</parameter>
+<parameter name="result">
+<parameter_description> a #GAsyncResult
+</parameter_description>
+</parameter>
+<parameter name="error">
+<parameter_description> a #GError, or %NULL
+</parameter_description>
+</parameter>
+</parameters>
+<return> %TRUE on successful directory creation, %FALSE otherwise.
+</return>
+</function>
+
 <function name="g_file_make_directory_with_parents">
 <description>
 Creates a directory and any parent directories that may not
@@ -40118,6 +40532,7 @@ If @cancellable is not %NULL, then the operation can be cancelled by
 triggering the cancellable object from another thread. If the operation
 was cancelled, the error %G_IO_ERROR_CANCELLED will be returned.
 
+Virtual: trash
 
 </description>
 <parameters>
@@ -40139,6 +40554,69 @@ was cancelled, the error %G_IO_ERROR_CANCELLED will be returned.
 </return>
 </function>
 
+<function name="g_file_trash_async">
+<description>
+Asynchronously sends @file to the Trash location, if possible.
+
+Virtual: trash_async
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="file">
+<parameter_description> input #GFile
+</parameter_description>
+</parameter>
+<parameter name="io_priority">
+<parameter_description> the &lt;link linkend=&quot;io-priority&quot;&gt;I/O priority&lt;/link&gt;
+of the request
+</parameter_description>
+</parameter>
+<parameter name="cancellable">
+<parameter_description> optional #GCancellable object,
+%NULL to ignore
+</parameter_description>
+</parameter>
+<parameter name="callback">
+<parameter_description> a #GAsyncReadyCallback to call
+when the request is satisfied
+</parameter_description>
+</parameter>
+<parameter name="user_data">
+<parameter_description> the data to pass to callback function
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
+<function name="g_file_trash_finish">
+<description>
+Finishes an asynchronous file trashing operation, started with
+g_file_trash_async().
+
+Virtual: trash_finish
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="file">
+<parameter_description> input #GFile
+</parameter_description>
+</parameter>
+<parameter name="result">
+<parameter_description> a #GAsyncResult
+</parameter_description>
+</parameter>
+<parameter name="error">
+<parameter_description> a #GError, or %NULL
+</parameter_description>
+</parameter>
+</parameters>
+<return> %TRUE on successful trash, %FALSE otherwise.
+</return>
+</function>
+
 <function name="g_file_unmount_mountable">
 <description>
 Unmounts a file of type G_FILE_TYPE_MOUNTABLE.
@@ -40466,6 +40944,24 @@ Sets whether the base stream will be closed when @stream is closed.
 <return></return>
 </function>
 
+<function name="g_icon_deserialize">
+<description>
+Deserializes a #GIcon previously serialized using g_icon_serialize().
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="value">
+<parameter_description> a #GVariant created with g_icon_serialize()
+</parameter_description>
+</parameter>
+</parameters>
+<return> a #GIcon, or %NULL when deserialization fails.
+
+</return>
+</function>
+
 <function name="g_icon_equal">
 <description>
 Checks if two icons are equal.
@@ -40532,6 +41028,28 @@ interface or %NULL if @error is set.
 </return>
 </function>
 
+<function name="g_icon_serialize">
+<description>
+Serializes a #GIcon into a #GVariant. An equivalent #GIcon can be retrieved
+back by calling g_icon_deserialize() on the returned value.
+As serialization will avoid using raw icon data when possible, it only
+makes sense to transfer the #GVariant between processes on the same machine,
+(as opposed to over the network), and within the same file system namespace.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="icon">
+<parameter_description> a #GIcon
+</parameter_description>
+</parameter>
+</parameters>
+<return> a #GVariant, or %NULL when serialization fails.
+
+</return>
+</function>
+
 <function name="g_icon_to_string">
 <description>
 Generates a textual representation of @icon that can be used for
@@ -44217,14 +44735,8 @@ Since: 2.32
 <description>
 Sets the &quot;action&quot; and possibly the &quot;target&quot; attribute of @menu_item.
 
-If @detailed_action contains a double colon (&quot;::&quot;) then it is used as
-a separator between an action name and a target string.  In this
-case, this call is equivalent to calling
-g_menu_item_set_action_and_target() with the part before the &quot;::&quot; and
-with a string-type #GVariant containing the part following the &quot;::&quot;.
-
-If @detailed_action doesn't contain &quot;::&quot; then the action is set to
-the given string (verbatim) and the target value is unset.
+The format of @detailed_action is the same format parsed by
+g_action_parse_detailed_name().
 
 See g_menu_item_set_action_and_target() or
 g_menu_item_set_action_and_target_value() for more flexible (but
@@ -44249,6 +44761,37 @@ Since: 2.32
 <return></return>
 </function>
 
+<function name="g_menu_item_set_icon">
+<description>
+Sets (or unsets) the icon on @menu_item.
+
+This call is the same as calling g_icon_serialize() and using the
+result as the value to g_menu_item_set_attribute_value() for
+%G_MENU_ATTRIBUTE_ICON.
+
+This API is only intended for use with &quot;noun&quot; menu items; things like
+bookmarks or applications in an &quot;Open With&quot; menu.  Don't use it on
+menu items corresponding to verbs (eg: stock icons for 'Save' or
+'Quit').
+
+If @icon is %NULL then the icon is unset.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="menu_item">
+<parameter_description> a #GMenuItem
+</parameter_description>
+</parameter>
+<parameter name="icon">
+<parameter_description> a #GIcon, or %NULL
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
 <function name="g_menu_item_set_label">
 <description>
 Sets or unsets the &quot;label&quot; attribute of @menu_item.
@@ -44859,6 +45402,22 @@ Since: 2.32
 <return></return>
 </function>
 
+<function name="g_menu_remove_all">
+<description>
+Removes all items in the menu.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="menu">
+<parameter_description> a #GMenu
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
 <function name="g_mount_can_eject">
 <description>
 Checks if @mount can be eject.
@@ -47839,6 +48398,39 @@ written to the stream
 </return>
 </function>
 
+<function name="g_property_action_new">
+<description>
+Creates a #GAction corresponding to the value of property
+ property_name on @object.
+
+The property must be existent and readable and writable (and not
+construct-only).
+
+This function takes a reference on @object and doesn't release it
+until the action is destroyed.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="name">
+<parameter_description> the name of the action to create
+</parameter_description>
+</parameter>
+<parameter name="object">
+<parameter_description> the object that has the property to wrap
+</parameter_description>
+</parameter>
+<parameter name="property_name">
+<parameter_description> the name of the property
+</parameter_description>
+</parameter>
+</parameters>
+<return> a new #GPropertyAction
+
+</return>
+</function>
+
 <function name="g_proxy_address_get_destination_hostname">
 <description>
 Gets @proxy's destination hostname; that is, the name of the host
@@ -51633,6 +52225,8 @@ of the action should not attempt to directly modify the 'state'
 property.  Instead, they should call g_action_change_state() to
 request the change.
 
+If the @value GVariant is floating, it is consumed.
+
 Since: 2.30
 
 </description>
@@ -52369,6 +52963,30 @@ Since: 2.36
 <return></return>
 </function>
 
+<function name="g_simple_proxy_resolver_set_ignore_hosts">
+<description>
+Sets the list of ignored hosts.
+
+See #GSimpleProxyResolver:ignore-hosts for more details on how the
+ ignore_hosts argument is interpreted.
+
+Since: 2.36
+
+</description>
+<parameters>
+<parameter name="resolver">
+<parameter_description> a #GSimpleProxyResolver
+</parameter_description>
+</parameter>
+<parameter name="ignore_hosts">
+<parameter_description> %NULL-terminated list of hosts/IP addresses
+to not use a proxy for
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
 <function name="g_simple_proxy_resolver_set_uri_proxy">
 <description>
 Adds a URI-scheme-specific proxy to @resolver; URIs whose scheme
diff --git a/glib/src/glib_docs.xml b/glib/src/glib_docs.xml
index 100a025..2541e15 100644
--- a/glib/src/glib_docs.xml
+++ b/glib/src/glib_docs.xml
@@ -452,10 +452,10 @@ library function.
 <parameter name="G_FILE_ERROR_PIPE">
 <parameter_description> Broken pipe; there is no process reading from the
 other end of a pipe. Every library function that returns this
-error code also generates a `SIGPIPE' signal; this signal
+error code also generates a 'SIGPIPE' signal; this signal
 terminates the program if not handled or blocked. Thus, your
 program will never actually see this code unless it has handled
-or blocked `SIGPIPE'.
+or blocked 'SIGPIPE'.
 </parameter_description>
 </parameter>
 <parameter name="G_FILE_ERROR_AGAIN">
@@ -1264,7 +1264,7 @@ direct control. Since 2.8.
 <enum name="GParamFlags">
 <description>
 Through the #GParamFlags flag values, certain aspects of parameters
-can be configured.
+can be configured. See also #G_PARAM_READWRITE and #G_PARAM_STATIC_STRINGS.
 
 </description>
 <parameters>
@@ -1843,7 +1843,7 @@ U+2029 PARAGRAPH SEPARATOR. Since: 2.34
 <parameter_description> Turns on the partial matching feature. In contrast to
 to #G_REGEX_MATCH_PARTIAL_SOFT, this stops matching as soon as a partial match
 is found, without continuing to search for a possible complete match. See
-see g_match_info_is_partial_match() for more information. Since: 2.34
+g_match_info_is_partial_match() for more information. Since: 2.34
 </parameter_description>
 </parameter>
 <parameter name="G_REGEX_MATCH_NOTEMPTY_ATSTART">
@@ -2140,11 +2140,81 @@ environment. Since: 2.34
 </parameters>
 </enum>
 
+<enum name="GTestFileType">
+<description>
+The type of file to return the filename for, when used with
+g_test_build_filename().
+
+These two options correspond rather directly to the 'dist' and
+'built' terminology that automake uses and are explicitly used to
+distinguish between the 'srcdir' and 'builddir' being separate.  All
+files in your project should either be dist (in the
+&lt;literal&gt;DIST_EXTRA&lt;/literal&gt; or &lt;literal&gt;dist_schema_DATA&lt;/literal&gt;
+sense, in which case they will always be in the srcdir) or built (in
+the &lt;literal&gt;BUILT_SOURCES&lt;/literal&gt; sense, in which case they will
+always be in the builddir).
+
+Note: as a general rule of automake, files that are generated only as
+part of the build-from-git process (but then are distributed with the
+tarball) always go in srcdir (even if doing a srcdir != builddir
+build from git) and are considered as distributed files.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="G_TEST_DIST">
+<parameter_description> a file that was included in the distribution tarball
+</parameter_description>
+</parameter>
+<parameter name="G_TEST_BUILT">
+<parameter_description> a file that was built on the compiling machine
+</parameter_description>
+</parameter>
+</parameters>
+</enum>
+
+<enum name="GTestSubprocessFlags">
+<description>
+Flags to pass to g_test_trap_subprocess() to control input and output.
+
+Note that in contrast with g_test_trap_fork(), the default is to
+not show stdout and stderr.
+
+</description>
+<parameters>
+<parameter name="G_TEST_SUBPROCESS_INHERIT_STDIN">
+<parameter_description> If this flag is given, the child
+process will inherit the parent's stdin. Otherwise, the child's
+stdin is redirected to &lt;filename&gt;/dev/null&lt;/filename&gt;.
+</parameter_description>
+</parameter>
+<parameter name="G_TEST_SUBPROCESS_INHERIT_STDOUT">
+<parameter_description> If this flag is given, the child
+process will inherit the parent's stdout. Otherwise, the child's
+stdout will not be visible, but it will be captured to allow
+later tests with g_test_trap_assert_stdout().
+</parameter_description>
+</parameter>
+<parameter name="G_TEST_SUBPROCESS_INHERIT_STDERR">
+<parameter_description> If this flag is given, the child
+process will inherit the parent's stderr. Otherwise, the child's
+stderr will not be visible, but it will be captured to allow
+later tests with g_test_trap_assert_stderr().
+</parameter_description>
+</parameter>
+</parameters>
+</enum>
+
 <enum name="GTestTrapFlags">
 <description>
 Test traps are guards around forked tests.
 These flags determine what traps to set.
 
+Deprecated: #GTestTrapFlags is used only with g_test_trap_fork(),
+which is deprecated. g_test_trap_subprocess() uses
+#GTestTrapSubprocessFlags.
+
 </description>
 <parameters>
 <parameter name="G_TEST_TRAP_SILENCE_STDOUT">
@@ -2163,7 +2233,7 @@ though to allow later tests with g_test_trap_assert_stderr().
 </parameter>
 <parameter name="G_TEST_TRAP_INHERIT_STDIN">
 <parameter_description> If this flag is given, stdin of the
-forked child process is shared with stdin of its parent process.
+child process is shared with stdin of its parent process.
 It is redirected to &lt;filename&gt;/dev/null&lt;/filename&gt; otherwise.
 </parameter_description>
 </parameter>
@@ -6348,6 +6418,28 @@ Since: 2.26
 </return>
 </function>
 
+<function name="g_binding_unbind">
+<description>
+Explicitly releases the binding between the source and the target
+property expressed by @binding.
+
+&lt;note&gt;This function will release the reference that is being held on
+the @binding instance; if you want to hold on to the #GBinding instance
+after calling g_binding_unbind(), you will need to hold a reference
+to it.&lt;/note&gt;
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="binding">
+<parameter_description> a #GBinding
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
 <function name="g_bit_lock">
 <description>
 Sets the indicated @lock_bit in @address.  If the bit is already
@@ -6658,7 +6750,7 @@ Since: 2.12
 </parameter_description>
 </parameter>
 <parameter name="exec">
-<parameter_description> location for the command line of the application, or %NULL
+<parameter_description> return location for the command line of the application, or %NULL
 </parameter_description>
 </parameter>
 <parameter name="count">
@@ -23300,8 +23392,34 @@ this thread is now the owner of @context.
 
 <function name="g_main_context_wakeup">
 <description>
-If @context is currently waiting in a poll(), interrupt
-the poll(), and continue the iteration process.
+If @context is currently blocking in g_main_context_iteration()
+waiting for a source to become ready, cause it to stop blocking
+and return.  Otherwise, cause the next invocation of
+g_main_context_iteration() to return without blocking.
+
+This API is useful for low-level control over #GMainContext; for
+example, integrating it with main loop implementations such as
+#GMainLoop.
+
+Another related use for this function is when implementing a main
+loop with a termination condition, computed from multiple threads:
+
+|[
+#define NUM_TASKS 10
+static volatile gint tasks_remaining = NUM_TASKS;
+...
+
+while (g_atomic_int_get (&amp;tasks_remaining) != 0)
+g_main_context_iteration (NULL, TRUE);
+]|
+
+Then in a thread:
+|[
+perform_work();
+
+if (g_atomic_int_dec_and_test (&amp;tasks_remaining))
+g_main_context_wakeup (NULL);
+]|
 
 </description>
 <parameters>
@@ -24909,19 +25027,11 @@ possible complete match, while with #G_REGEX_MATCH_PARTIAL_HARD matching
 stops at the partial match.
 When both #G_REGEX_MATCH_PARTIAL_SOFT and #G_REGEX_MATCH_PARTIAL_HARD
 are set, the latter takes precedence.
-See &lt;ulink&gt;man:pcrepartial&lt;/ulink&gt; for more information on partial matching.
 
-Because of the way certain internal optimizations are implemented
-the partial matching algorithm cannot be used with all patterns.
-So repeated single characters such as &quot;a{2,4}&quot; and repeated single
-meta-sequences such as &quot;\d+&quot; are not permitted if the maximum number
-of occurrences is greater than one. Optional items such as &quot;\d?&quot;
-(where the maximum is one) are permitted. Quantifiers with any values
-are permitted after parentheses, so the invalid examples above can be
-coded thus &quot;(a){2,4}&quot; and &quot;(\d)+&quot;. If #G_REGEX_MATCH_PARTIAL or 
-#G_REGEX_MATCH_PARTIAL_HARD is set
-for a pattern that does not conform to the restrictions, matching
-functions return an error.
+There were formerly some restrictions on the pattern for partial matching.
+The restrictions no longer apply.
+
+See &lt;ulink&gt;man:pcrepartial&lt;/ulink&gt; for more information on partial matching.
 
 Since: 2.14
 
@@ -27761,7 +27871,7 @@ operation, for user data on an object.
 
 If the previous value was replaced then ownership of the
 old value (@oldval) is passed to the caller, including
-the registred destroy notify for it (passed out in @old_destroy).
+the registered destroy notify for it (passed out in @old_destroy).
 Its up to the caller to free this as he wishes, which may
 or may not include using @old_destroy as sometimes replacement
 should not destroy the object in the normal way.
@@ -27812,7 +27922,7 @@ operation, for user data on an object.
 
 If the previous value was replaced then ownership of the
 old value (@oldval) is passed to the caller, including
-the registred destroy notify for it (passed out in @old_destroy).
+the registered destroy notify for it (passed out in @old_destroy).
 Its up to the caller to free this as he wishes, which may
 or may not include using @old_destroy as sometimes replacement
 should not destroy the object in the normal way.
@@ -29142,6 +29252,26 @@ Since: 2.6
 <return></return>
 </function>
 
+<function name="g_param_get_default_value">
+<description>
+Gets the default value of @param as a pointer to a #GValue.
+
+The #GValue will remain value for the life of @param.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="param">
+<parameter_description> a #GParamSpec
+</parameter_description>
+</parameter>
+</parameters>
+<return> a pointer to a #GValue which must not be modified
+
+</return>
+</function>
+
 <function name="g_param_spec_boolean">
 <description>
 Creates a new #GParamSpecBoolean instance specifying a %G_TYPE_BOOLEAN
@@ -33353,6 +33483,26 @@ Since: 2.14
 </return>
 </function>
 
+<function name="g_regex_get_max_lookbehind">
+<description>
+Gets the number of characters in the longest lookbehind assertion in the
+pattern. This information is useful when doing multi-segment matching using
+the partial matching facilities.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="regex">
+<parameter_description> a #GRegex structure
+</parameter_description>
+</parameter>
+</parameters>
+<return> the number of characters in the longest lookbehind assertion.
+
+</return>
+</function>
+
 <function name="g_regex_get_pattern">
 <description>
 Gets the pattern string associated with @regex, i.e. a copy of
@@ -37918,7 +38068,7 @@ for the signal.
 <description>
 Overrides the class closure (i.e. the default handler) for the
 given signal for emissions on instances of @instance_type with
-callabck @class_handler. @instance_type must be derived from the
+callback @class_handler. @instance_type must be derived from the
 type to which the signal belongs.
 
 See g_signal_chain_from_overridden() and
@@ -40500,7 +40650,7 @@ if those parameters are non-%NULL. Note that you must set the
 passing %NULL for @standard_output and @standard_error.
 
 If @exit_status is non-%NULL, the platform-specific exit status of
-the child is stored there; see the doucumentation of
+the child is stored there; see the documentation of
 g_spawn_check_exit_status() for how to use and interpret this.
 Note that it is invalid to pass %G_SPAWN_DO_NOT_REAP_CHILD in
 @flags.
@@ -43261,6 +43411,11 @@ created on the fly and added to the root fixture, based on the
 slash-separated portions of @testpath. The @test_data argument
 will be passed as first argument to @test_func.
 
+If @testpath includes the component &quot;subprocess&quot; anywhere in it,
+the test will be skipped by default, and only run if explicitly
+required via the &lt;option&gt;-p&lt;/option&gt; command-line option or
+g_test_trap_subprocess().
+
 Since: 2.16
 
 </description>
@@ -43317,6 +43472,11 @@ the test is assumed to use no fixture, and test suites are automatically
 created on the fly and added to the root fixture, based on the
 slash-separated portions of @testpath.
 
+If @testpath includes the component &quot;subprocess&quot; anywhere in it,
+the test will be skipped by default, and only run if explicitly
+required via the &lt;option&gt;-p&lt;/option&gt; command-line option or
+g_test_trap_subprocess().
+
 Since: 2.16
 
 </description>
@@ -43391,6 +43551,53 @@ Since: 2.16
 <return></return>
 </function>
 
+<function name="g_test_build_filename">
+<description>
+Creates the pathname to a data file that is required for a test.
+
+This function is conceptually similar to g_build_filename() except
+that the first argument has been replaced with a #GTestFileType
+argument.
+
+The data file should either have been distributed with the module
+containing the test (%G_TEST_DIST) or built as part of the build
+system of that module (%G_TEST_BUILT).
+
+In order for this function to work in srcdir != builddir situations,
+the G_TEST_SRCDIR and G_TEST_BUILDDIR environment variables need to
+have been defined.  As of 2.38, this is done by the Makefile.decl
+included in GLib.  Please ensure that your copy is up to date before
+using this function.
+
+In case neither variable is set, this function will fall back to
+using the dirname portion of argv[0], possibly removing &quot;.libs&quot;.
+This allows for casual running of tests directly from the commandline
+in the srcdir == builddir case and should also support running of
+installed tests, assuming the data files have been installed in the
+same relative path as the test binary.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="file_type">
+<parameter_description> the type of file (built vs. distributed)
+</parameter_description>
+</parameter>
+<parameter name="first_path">
+<parameter_description> the first segment of the pathname
+</parameter_description>
+</parameter>
+<parameter name="Varargs">
+<parameter_description> %NULL-terminated additional path segments
+</parameter_description>
+</parameter>
+</parameters>
+<return> the path of the file, to be freed using g_free()
+
+</return>
+</function>
+
 <function name="g_test_create_case">
 <description>
 Create a new #GTestCase, named @test_name, this API is fairly
@@ -43489,7 +43696,7 @@ g_test_assert_expected_messages ();
 
 Note that you cannot use this to test g_error() messages, since
 g_error() intentionally never returns even if the program doesn't
-abort; use g_test_trap_fork() in this case.
+abort; use g_test_trap_subprocess() in this case.
 
 Since: 2.34
 
@@ -43536,6 +43743,65 @@ Since: 2.30
 <return></return>
 </function>
 
+<function name="g_test_get_dir">
+<description>
+Gets the pathname of the directory containing test files of the type
+specified by @file_type.
+
+This is approximately the same as calling g_test_build_filename(&quot;.&quot;),
+but you don't need to free the return value.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="file_type">
+<parameter_description> the type of file (built vs. distributed)
+</parameter_description>
+</parameter>
+</parameters>
+<return> the path of the directory, owned by GLib
+
+</return>
+</function>
+
+<function name="g_test_get_filename">
+<description>
+Gets the pathname to a data file that is required for a test.
+
+This is the same as g_test_build_filename() with two differences.
+The first difference is that must only use this function from within
+a testcase function.  The second difference is that you need not free
+the return value -- it will be automatically freed when the testcase
+finishes running.
+
+It is safe to use this function from a thread inside of a testcase
+but you must ensure that all such uses occur before the main testcase
+function returns (ie: it is best to ensure that all threads have been
+joined).
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="file_type">
+<parameter_description> the type of file (built vs. distributed)
+</parameter_description>
+</parameter>
+<parameter name="first_path">
+<parameter_description> the first segment of the pathname
+</parameter_description>
+</parameter>
+<parameter name="Varargs">
+<parameter_description> %NULL-terminated additional path segments
+</parameter_description>
+</parameter>
+</parameters>
+<return> the path, automatically freed at the end of the testcase
+
+</return>
+</function>
+
 <function name="g_test_get_root">
 <description>
 Get the toplevel test suite for the test path API.
@@ -43581,6 +43847,8 @@ Provide a random seed to reproduce test runs using random numbers.
 &lt;term&gt;&lt;option&gt;-p &lt;replaceable&gt;TESTPATH&lt;/replaceable&gt;&lt;/option&gt;&lt;/term&gt;
 &lt;listitem&gt;&lt;para&gt;
 Execute all tests matching &lt;replaceable&gt;TESTPATH&lt;/replaceable&gt;.
+This can also be used to force a test to run that would otherwise
+be skipped (ie, a test whose name contains &quot;/subprocess&quot;).
 &lt;/para&gt;&lt;/listitem&gt;
 &lt;/varlistentry&gt;
 &lt;varlistentry&gt;
@@ -43611,8 +43879,8 @@ Quick tests, should run really quickly and give good coverage.
 &lt;term&gt;undefined&lt;/term&gt;
 &lt;listitem&gt;&lt;para&gt;
 Tests for undefined behaviour, may provoke programming errors
-under g_test_trap_fork() to check that appropriate assertions
-or warnings are given
+under g_test_trap_subprocess() or g_test_expect_messages() to check
+that appropriate assertions or warnings are given
 &lt;/para&gt;&lt;/listitem&gt;
 &lt;/varlistentry&gt;
 &lt;varlistentry&gt;
@@ -44079,6 +44347,22 @@ there is no &quot;medium speed&quot;.
 </return>
 </function>
 
+<function name="g_test_subprocess">
+<description>
+Returns %TRUE (after g_test_init() has been called) if the test
+program is running under g_test_trap_subprocess().
+
+Since: 2.38
+
+</description>
+<parameters>
+</parameters>
+<return> %TRUE if the test program is running under
+g_test_trap_subprocess().
+
+</return>
+</function>
+
 <function name="g_test_suite_add">
 <description>
 Adds @test_case to @suite.
@@ -44175,13 +44459,13 @@ Since: 2.16
 
 <function name="g_test_trap_assert_failed">
 <description>
-Assert that the last forked test failed.
-See g_test_trap_fork().
+Assert that the last test subprocess failed.
+See g_test_trap_subprocess().
 
 This is sometimes used to test situations that are formally considered to
 be undefined behaviour, like inputs that fail a g_return_if_fail()
 check. In these situations you should skip the entire test, including the
-call to g_test_trap_fork(), unless g_test_undefined() returns %TRUE
+call to g_test_trap_subprocess(), unless g_test_undefined() returns %TRUE
 to indicate that undefined behaviour may be tested.
 
 Since: 2.16
@@ -44194,8 +44478,8 @@ Since: 2.16
 
 <function name="g_test_trap_assert_passed">
 <description>
-Assert that the last forked test passed.
-See g_test_trap_fork().
+Assert that the last test subprocess passed.
+See g_test_trap_subprocess().
 
 Since: 2.16
 
@@ -44207,14 +44491,15 @@ Since: 2.16
 
 <function name="g_test_trap_assert_stderr">
 <description>
-Assert that the stderr output of the last forked test
-matches @serrpattern. See  g_test_trap_fork().
+Assert that the stderr output of the last test subprocess
+matches @serrpattern. See  g_test_trap_subprocess().
 
-This is sometimes used to test situations that are formally considered to
-be undefined behaviour, like inputs that fail a g_return_if_fail()
-check. In these situations you should skip the entire test, including the
-call to g_test_trap_fork(), unless g_test_undefined() returns %TRUE
-to indicate that undefined behaviour may be tested.
+This is sometimes used to test situations that are formally
+considered to be undefined behaviour, like code that hits a
+g_assert() or g_error(). In these situations you should skip the
+entire test, including the call to g_test_trap_subprocess(), unless
+g_test_undefined() returns %TRUE to indicate that undefined
+behaviour may be tested.
 
 Since: 2.16
 
@@ -44231,8 +44516,8 @@ Since: 2.16
 
 <function name="g_test_trap_assert_stderr_unmatched">
 <description>
-Assert that the stderr output of the last forked test
-does not match @serrpattern. See g_test_trap_fork().
+Assert that the stderr output of the last test subprocess
+does not match @serrpattern. See g_test_trap_subprocess().
 
 Since: 2.16
 
@@ -44249,8 +44534,8 @@ Since: 2.16
 
 <function name="g_test_trap_assert_stdout">
 <description>
-Assert that the stdout output of the last forked test matches
- soutpattern  See g_test_trap_fork().
+Assert that the stdout output of the last test subprocess matches
+ soutpattern  See g_test_trap_subprocess().
 
 Since: 2.16
 
@@ -44267,8 +44552,8 @@ Since: 2.16
 
 <function name="g_test_trap_assert_stdout_unmatched">
 <description>
-Assert that the stdout output of the last forked test
-does not match @soutpattern. See g_test_trap_fork().
+Assert that the stdout output of the last test subprocess
+does not match @soutpattern. See g_test_trap_subprocess().
 
 Since: 2.16
 
@@ -44286,8 +44571,10 @@ Since: 2.16
 <function name="g_test_trap_fork">
 <description>
 Fork the current test program to execute a test case that might
-not return or that might abort. The forked test case is aborted
-and considered failing if its run time exceeds @usec_timeout.
+not return or that might abort.
+
+If @usec_timeout is non-0, the forked test case is aborted and
+considered failing if its run time exceeds it.
 
 The forking behavior can be configured with the #GTestTrapFlags flags.
 
@@ -44306,16 +44593,18 @@ g_print (&quot;some stdout text: somagic17\n&quot;);
 g_printerr (&quot;some stderr text: semagic43\n&quot;);
 exit (0); / * successful test run * /
 }
-g_test_trap_assert_passed();
+g_test_trap_assert_passed ();
 g_test_trap_assert_stdout (&quot;*somagic17*&quot;);
 g_test_trap_assert_stderr (&quot;*semagic43*&quot;);
 }
 ]|
 
-This function is implemented only on Unix platforms.
-
 Since: 2.16
 
+Deprecated: This function is implemented only on Unix platforms,
+and is not always reliable due to problems inherent in
+fork-without-exec. Use g_test_trap_subprocess() instead.
+
 </description>
 <parameters>
 <parameter name="usec_timeout">
@@ -44334,38 +44623,121 @@ Since: 2.16
 
 <function name="g_test_trap_has_passed">
 <description>
-Check the result of the last g_test_trap_fork() call.
+Check the result of the last g_test_trap_subprocess() call.
 
 Since: 2.16
 
 </description>
 <parameters>
 </parameters>
-<return> %TRUE if the last forked child terminated successfully.
+<return> %TRUE if the last test subprocess terminated successfully.
 
 </return>
 </function>
 
 <function name="g_test_trap_reached_timeout">
 <description>
-Check the result of the last g_test_trap_fork() call.
+Check the result of the last g_test_trap_subprocess() call.
 
 Since: 2.16
 
 </description>
 <parameters>
 </parameters>
-<return> %TRUE if the last forked child got killed due to a fork timeout.
+<return> %TRUE if the last test subprocess got killed due to a timeout.
 
 </return>
 </function>
 
+<function name="g_test_trap_subprocess">
+<description>
+Respawns the test program to run only @test_path in a subprocess.
+This can be used for a test case that might not return, or that
+might abort. @test_path will normally be the name of the parent
+test, followed by &quot;&lt;literal&gt;/subprocess/&lt;/literal&gt;&quot; and then a name
+for the specific subtest (or just ending with
+&quot;&lt;literal&gt;/subprocess&lt;/literal&gt;&quot; if the test only has one child
+test); tests with names of this form will automatically be skipped
+in the parent process.
+
+If @usec_timeout is non-0, the test subprocess is aborted and
+considered failing if its run time exceeds it.
+
+The subprocess behavior can be configured with the
+#GTestSubprocessFlags flags.
+
+You can use methods such as g_test_trap_assert_passed(),
+g_test_trap_assert_failed(), and g_test_trap_assert_stderr() to
+check the results of the subprocess. (But note that
+g_test_trap_assert_stdout() and g_test_trap_assert_stderr()
+cannot be used if @test_flags specifies that the child should
+inherit the parent stdout/stderr.) 
+
+If your &lt;literal&gt;main ()&lt;/literal&gt; needs to behave differently in
+the subprocess, you can call g_test_subprocess() (after calling
+g_test_init()) to see whether you are in a subprocess.
+
+The following example tests that calling
+&lt;literal&gt;my_object_new(1000000)&lt;/literal&gt; will abort with an error
+message.
+
+|[
+static void
+test_create_large_object_subprocess (void)
+{
+my_object_new (1000000);
+}
+
+static void
+test_create_large_object (void)
+{
+g_test_trap_subprocess (&quot;/myobject/create_large_object/subprocess&quot;, 0, 0);
+g_test_trap_assert_failed ();
+g_test_trap_assert_stderr (&quot;*ERROR*too large*&quot;);
+}
+
+int
+main (int argc, char **argv)
+{
+g_test_init (&amp;argc, &amp;argv, NULL);
+
+g_test_add_func (&quot;/myobject/create_large_object&quot;,
+test_create_large_object);
+/ * Because of the '/subprocess' in the name, this test will
+* not be run by the g_test_run () call below.
+* /
+g_test_add_func (&quot;/myobject/create_large_object/subprocess&quot;,
+test_create_large_object_subprocess);
+
+return g_test_run ();
+}
+]|
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="test_path">
+<parameter_description>    Test to run in a subprocess
+</parameter_description>
+</parameter>
+<parameter name="usec_timeout">
+<parameter_description> Timeout for the subprocess test in micro seconds.
+</parameter_description>
+</parameter>
+<parameter name="test_flags">
+<parameter_description>   Flags to modify subprocess behaviour.
+</parameter_description>
+</parameter>
+</parameters>
+<return></return>
+</function>
+
 <function name="g_test_undefined">
 <description>
 Returns %TRUE if tests may provoke assertions and other formally-undefined
-behaviour under g_test_trap_fork(), to verify that appropriate warnings
-are given. It can be useful to turn this off if running tests under
-valgrind.
+behaviour, to verify that appropriate warnings are given. It might, in some
+cases, be useful to turn this off if running tests under valgrind.
 
 
 </description>
@@ -46938,6 +47310,31 @@ Since: 2.4
 <return></return>
 </function>
 
+<function name="g_type_class_get_instance_private_offset">
+<description>
+Gets the offset of the private data for instances of @g_class.
+
+This is how many bytes you should add to the instance pointer of a
+class in order to get the private data for the type represented by
+ g_class 
+
+You can only call this function after you have registered a private
+data area for @g_class using g_type_class_add_private().
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="g_class">
+<parameter_description> a #GTypeClass
+</parameter_description>
+</parameter>
+</parameters>
+<return> the offset, in bytes
+
+</return>
+</function>
+
 <function name="g_type_class_peek">
 <description>
 This function is essentially the same as g_type_class_ref(), except that
@@ -47323,11 +47720,11 @@ be retrieved from a subtype using g_type_get_qdata().
 
 <function name="g_type_get_type_registration_serial">
 <description>
-Returns an opaque serial number that represents the state of the set of registered
-types. Any time a type is registred this serial changes, which means you can
-cache information based on type lookups (such as g_type_from_name) and know if
-the cache is still valid at a later time by comparing the current serial with
-the one at the type lookup.
+Returns an opaque serial number that represents the state of the set of
+registered types. Any time a type is registered this serial changes,
+which means you can cache information based on type lookups (such as
+g_type_from_name()) and know if the cache is still valid at a later
+time by comparing the current serial with the one at the type lookup.
 
 Since: 2.36
 
@@ -49411,8 +49808,8 @@ Since: 2.16
 </parameter_description>
 </parameter>
 <parameter name="reserved_chars_allowed">
-<parameter_description> a string of reserved characters that are
-allowed to be used, or %NULL.
+<parameter_description> a string of reserved characters that
+are allowed to be used, or %NULL.
 </parameter_description>
 </parameter>
 <parameter name="allow_utf8">
@@ -49525,7 +49922,8 @@ Since: 2.16
 </parameter_description>
 </parameter>
 <parameter name="illegal_characters">
-<parameter_description> an optional string of illegal characters not to be allowed.
+<parameter_description> a string of illegal characters not to be
+allowed, or %NULL.
 </parameter_description>
 </parameter>
 </parameters>
@@ -50609,7 +51007,8 @@ linkend=&quot;GValueArray.n-values&quot;&gt;n_values&lt;/link&gt;&lt;/code&gt;
 Sort @value_array using @compare_func to compare the elements according to
 the semantics of #GCompareFunc.
 
-The current implementation uses Quick-Sort as sorting algorithm.
+The current implementation uses the same sorting algorithm as standard
+C qsort() function.
 
 Deprecated: 2.32: Use #GArray and g_array_sort().
 
@@ -50634,7 +51033,8 @@ Deprecated: 2.32: Use #GArray and g_array_sort().
 Sort @value_array using @compare_func to compare the elements according
 to the semantics of #GCompareDataFunc.
 
-The current implementation uses Quick-Sort as sorting algorithm.
+The current implementation uses the same sorting algorithm as standard
+C qsort() function.
 
 Deprecated: 2.32: Use #GArray and g_array_sort_with_data().
 
@@ -54590,6 +54990,33 @@ or by passing it to another g_variant_new() call.
 </return>
 </function>
 
+<function name="g_variant_new_printf">
+<description>
+Creates a string-type GVariant using printf formatting.
+
+This is similar to calling g_strdup_printf() and then
+g_variant_new_string() but it saves a temporary variable and an
+unnecessary copy.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="format_string">
+<parameter_description> a printf-style format string
+</parameter_description>
+</parameter>
+<parameter name="Varargs">
+<parameter_description> arguments for @format_string
+</parameter_description>
+</parameter>
+</parameters>
+<return> a floating reference to a new string
+#GVariant instance
+
+</return>
+</function>
+
 <function name="g_variant_new_signature">
 <description>
 Creates a D-Bus type signature #GVariant with the contents of
@@ -54655,6 +55082,34 @@ Since: 2.24
 </return>
 </function>
 
+<function name="g_variant_new_take_string">
+<description>
+Creates a string #GVariant with the contents of @string.
+
+ string must be valid utf8.
+
+This function consumes @string.  g_free() will be called on @string
+when it is no longer required.
+
+You must not modify or access @string in any other way after passing
+it to this function.  It is even possible that @string is immediately
+freed.
+
+Since: 2.38
+
+</description>
+<parameters>
+<parameter name="string">
+<parameter_description> a normal utf8 nul-terminated string
+</parameter_description>
+</parameter>
+</parameters>
+<return> a floating reference to a new string
+#GVariant instance
+
+</return>
+</function>
+
 <function name="g_variant_new_tuple">
 <description>
 Creates a new tuple #GVariant out of the items in @children.  The


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]