glib2 3.0.9-x86-mingw32 → 3.1.0-x86-mingw32

data/vendor/local/share/gtk-doc/html/glib/glib-Testing.html

@@ -725,8 +725,8 @@ nicely formatted test reports.</p>
 <span class="function">my_object_fixture_tear_down</span> <span class="gtkdoc opt">(</span>MyObjectFixture <span class="gtkdoc opt">*</span>fixture<span class="gtkdoc opt">,</span>
                              gconstpointer user_data<span class="gtkdoc opt">)</span>
 <span class="gtkdoc opt">{</span>
-  <span class="function"><a href="../gobject-The-Base-Object-Type.html#g-clear-object">g_clear_object</a></span> <span class="gtkdoc opt">(&amp;</span>fixture<span class="gtkdoc opt">-&gt;</span>helper<span class="gtkdoc opt">);</span>
-  <span class="function"><a href="../gobject-The-Base-Object-Type.html#g-clear-object">g_clear_object</a></span> <span class="gtkdoc opt">(&amp;</span>fixture<span class="gtkdoc opt">-&gt;</span>obj<span class="gtkdoc opt">);</span>
+  <span class="function"><a href="https://developer.gnome.org/gobject/unstable/gobject-The-Base-Object-Type.html#g-clear-object">g_clear_object</a></span> <span class="gtkdoc opt">(&amp;</span>fixture<span class="gtkdoc opt">-&gt;</span>helper<span class="gtkdoc opt">);</span>
+  <span class="function"><a href="https://developer.gnome.org/gobject/unstable/gobject-The-Base-Object-Type.html#g-clear-object">g_clear_object</a></span> <span class="gtkdoc opt">(&amp;</span>fixture<span class="gtkdoc opt">-&gt;</span>obj<span class="gtkdoc opt">);</span>
 <span class="gtkdoc opt">}</span>
 
 <span class="gtkdoc kwb">static void</span>
@@ -871,7 +871,8 @@ and parsing test related command line args.</p>
 runs using random numbers.</p></li>
 <li class="listitem"><p><code class="literal">--verbose</code>: Run tests verbosely.</p></li>
 <li class="listitem"><p><code class="literal">-q</code>, <code class="literal">--quiet</code>: Run tests quietly.</p></li>
-<li class="listitem"><p><code class="literal">-p PATH</code>: Execute all tests matching the given path.
+<li class="listitem"><p><code class="literal">-p PATH</code>: Execute all tests matching the given path.</p></li>
+<li class="listitem"><p><code class="literal">-s PATH</code>: Skip all tests matching the given path.
 This can also be used to force a test to run that would otherwise
 be skipped (ie, a test whose name contains "/subprocess").</p></li>
 <li class="listitem">
@@ -880,7 +881,7 @@ be skipped (ie, a test whose name contains "/subprocess").</p></li>
 <p><code class="literal">slow</code>, <code class="literal">thorough</code>: Slow and thorough tests, may take quite long and maximize coverage.</p>
 <p><code class="literal">quick</code>: Quick tests, should run really quickly and give good coverage.</p>
 <p><code class="literal">undefined</code>: Tests for undefined behaviour, may provoke programming errors
-under <a class="link" href="glib-Testing.html#g-test-trap-subprocess" title="g_test_trap_subprocess ()"><code class="function">g_test_trap_subprocess()</code></a> or <a href="glib-Testing.html#g-test-expect-message"><code class="function">g_test_expect_messages()</code></a> to check
+under <a class="link" href="glib-Testing.html#g-test-trap-subprocess" title="g_test_trap_subprocess ()"><code class="function">g_test_trap_subprocess()</code></a> or <a class="link" href="glib-Testing.html#g-test-expect-message" title="g_test_expect_message ()"><code class="function">g_test_expect_message()</code></a> to check
 that appropriate assertions or warnings are given</p>
 <p><code class="literal">no-undefined</code>: Avoid tests for undefined behaviour</p>
 </li>
@@ -1033,8 +1034,9 @@ g_test_run (<em class="parameter"><code><span class="type">void</span></code></e
 <p>Runs all tests under the toplevel suite which can be retrieved
 with <a class="link" href="glib-Testing.html#g-test-get-root" title="g_test_get_root ()"><code class="function">g_test_get_root()</code></a>. Similar to <a class="link" href="glib-Testing.html#g-test-run-suite" title="g_test_run_suite ()"><code class="function">g_test_run_suite()</code></a>, the test
 cases to be run are filtered according to test path arguments
-(<code class="literal">-p testpath</code>) as parsed by <a class="link" href="glib-Testing.html#g-test-init" title="g_test_init ()"><code class="function">g_test_init()</code></a>. <a class="link" href="glib-Testing.html#g-test-run-suite" title="g_test_run_suite ()"><code class="function">g_test_run_suite()</code></a>
-or <a class="link" href="glib-Testing.html#g-test-run" title="g_test_run ()"><code class="function">g_test_run()</code></a> may only be called once in a program.</p>
+(<code class="literal">-p testpath</code> and <code class="literal">-s testpath</code>) as parsed by <a class="link" href="glib-Testing.html#g-test-init" title="g_test_init ()"><code class="function">g_test_init()</code></a>.
+<a class="link" href="glib-Testing.html#g-test-run-suite" title="g_test_run_suite ()"><code class="function">g_test_run_suite()</code></a> or <a class="link" href="glib-Testing.html#g-test-run" title="g_test_run ()"><code class="function">g_test_run()</code></a> may only be called once in a
+program.</p>
 <p>In general, the tests and sub-suites within each suite are run in
 the order in which they are defined. However, note that prior to
 GLib 2.36, there was a bug in the <code class="literal">g_test_add_*</code>
@@ -1420,7 +1422,8 @@ but you don't need to free the return value.</p>
 </div>
 <div class="refsect3">
 <a name="g-test-get-dir.returns"></a><h4>Returns</h4>
-<p> the path of the directory, owned by GLib</p>
+<p> the path of the directory, owned by GLib. </p>
+<p><span class="annotation">[<acronym title="Override the parsed C type with given type."><span class="acronym">type</span></acronym> filename]</span></p>
 </div>
 <p class="since">Since: <a class="link" href="api-index-2-38.html#api-index-2.38">2.38</a></p>
 </div>
@@ -1676,6 +1679,11 @@ domain and message to precisely not abort in such a case.</p>
 any test case, so you have to set it inside each test
 function which needs the special behavior.</p>
 <p>This handler has no effect on g_error messages.</p>
+<p>This handler also has no effect on structured log messages (using
+<a class="link" href="glib-Message-Logging.html#g-log-structured" title="g_log_structured ()"><code class="function">g_log_structured()</code></a> or <a class="link" href="glib-Message-Logging.html#g-log-structured-array" title="g_log_structured_array ()"><code class="function">g_log_structured_array()</code></a>). To change the fatal
+behaviour for specific log messages, programs must install a custom log
+writer function using <a class="link" href="glib-Message-Logging.html#g-log-set-writer-func" title="g_log_set_writer_func ()"><code class="function">g_log_set_writer_func()</code></a>.See
+Using Structured Logging.</p>
 <div class="refsect3">
 <a name="g-test-log-set-fatal-handler.parameters"></a><h4>Parameters</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
@@ -1799,9 +1807,9 @@ callback A before callback B will cause <code class="function">B()</code> to be
 <div class="refsect2">
 <a name="g-test-queue-unref"></a><h3>g_test_queue_unref()</h3>
 <pre class="programlisting">#define             g_test_queue_unref(gobject)</pre>
-<p>Enqueue an object to be released with <a href="../gobject-The-Base-Object-Type.html#g-object-unref"><code class="function">g_object_unref()</code></a> during
+<p>Enqueue an object to be released with <a href="https://developer.gnome.org/gobject/unstable/gobject-The-Base-Object-Type.html#g-object-unref"><code class="function">g_object_unref()</code></a> during
 the next teardown phase. This is equivalent to calling
-<a class="link" href="glib-Testing.html#g-test-queue-destroy" title="g_test_queue_destroy ()"><code class="function">g_test_queue_destroy()</code></a> with a destroy callback of <a href="../gobject-The-Base-Object-Type.html#g-object-unref"><code class="function">g_object_unref()</code></a>.</p>
+<a class="link" href="glib-Testing.html#g-test-queue-destroy" title="g_test_queue_destroy ()"><code class="function">g_test_queue_destroy()</code></a> with a destroy callback of <a href="https://developer.gnome.org/gobject/unstable/gobject-The-Base-Object-Type.html#g-object-unref"><code class="function">g_object_unref()</code></a>.</p>
 <div class="refsect3">
 <a name="g-test-queue-unref.parameters"></a><h4>Parameters</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
@@ -1833,6 +1841,9 @@ with text matching <em class="parameter"><code>pattern</code></em>
 , is expected to be logged. When this
 message is logged, it will not be printed, and the test case will
 not abort.</p>
+<p>This API may only be used with the old logging API (<a class="link" href="glib-Message-Logging.html#g-log" title="g_log ()"><code class="function">g_log()</code></a> without
+<code class="literal">G_LOG_USE_STRUCTURED</code> defined). It will not work with the structured logging
+API. See Testing for Messages.</p>
 <p>Use <a class="link" href="glib-Testing.html#g-test-assert-expected-messages" title="g_test_assert_expected_messages"><code class="function">g_test_assert_expected_messages()</code></a> to assert that all
 previously-expected messages have been seen and suppressed.</p>
 <p>You can call this multiple times in a row, if multiple messages are
@@ -1903,6 +1914,9 @@ expected via <a class="link" href="glib-Testing.html#g-test-expect-message" titl
 <pre class="programlisting">#define             g_test_assert_expected_messages()</pre>
 <p>Asserts that all messages previously indicated via
 <a class="link" href="glib-Testing.html#g-test-expect-message" title="g_test_expect_message ()"><code class="function">g_test_expect_message()</code></a> have been seen and suppressed.</p>
+<p>This API may only be used with the old logging API (<a class="link" href="glib-Message-Logging.html#g-log" title="g_log ()"><code class="function">g_log()</code></a> without
+<code class="literal">G_LOG_USE_STRUCTURED</code> defined). It will not work with the structured logging
+API. See Testing for Messages.</p>
 <p>If messages at <a class="link" href="glib-Message-Logging.html#G-LOG-LEVEL-DEBUG:CAPS"><code class="literal">G_LOG_LEVEL_DEBUG</code></a> are emitted, but not explicitly
 expected via <a class="link" href="glib-Testing.html#g-test-expect-message" title="g_test_expect_message ()"><code class="function">g_test_expect_message()</code></a> then they will be ignored.</p>
 <p class="since">Since: <a class="link" href="api-index-2-34.html#api-index-2.34">2.34</a></p>
@@ -3119,9 +3133,9 @@ g_test_run_suite (<em class="parameter"><code><a class="link" href="glib-Testing
 <p>Execute the tests within <em class="parameter"><code>suite</code></em>
  and all nested <a href="glib-Testing.html#GTestSuite"><span class="type">GTestSuites</span></a>.
 The test suites to be executed are filtered according to
-test path arguments (<code class="literal">-p testpath</code>) as parsed by <a class="link" href="glib-Testing.html#g-test-init" title="g_test_init ()"><code class="function">g_test_init()</code></a>.
-See the <a class="link" href="glib-Testing.html#g-test-run" title="g_test_run ()"><code class="function">g_test_run()</code></a> documentation for more information on the
-order that tests are run in.</p>
+test path arguments (<code class="literal">-p testpath</code> and <code class="literal">-s testpath</code>) as parsed by
+<a class="link" href="glib-Testing.html#g-test-init" title="g_test_init ()"><code class="function">g_test_init()</code></a>. See the <a class="link" href="glib-Testing.html#g-test-run" title="g_test_run ()"><code class="function">g_test_run()</code></a> documentation for more
+information on the order that tests are run in.</p>
 <p>g_test_run_suite() or <a class="link" href="glib-Testing.html#g-test-run" title="g_test_run ()"><code class="function">g_test_run()</code></a> may only be called once
 in a program.</p>
 <div class="refsect3">
@@ -3156,7 +3170,7 @@ in a program.</p>
 '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
-<code class="literal">DIST_EXTRA</code> or <code class="literal">dist_schema_DATA</code>
+<code class="literal">EXTRA_DIST</code> or <code class="literal">dist_schema_DATA</code>
 sense, in which case they will always be in the srcdir) or built (in
 the <code class="literal">BUILT_SOURCES</code> sense, in which case they will
 always be in the builddir).</p>

data/vendor/local/share/gtk-doc/html/glib/glib-The-Main-Event-Loop.html

@@ -840,6 +840,10 @@
 <td class="function_name"><a class="link" href="glib-The-Main-Event-Loop.html#GPid" title="GPid">GPid</a></td>
 </tr>
 <tr>
+<td class="define_keyword">#define</td>
+<td class="function_name"><a class="link" href="glib-The-Main-Event-Loop.html#G-PID-FORMAT:CAPS" title="G_PID_FORMAT">G_PID_FORMAT</a></td>
+</tr>
+<tr>
 <td class="datatype_keyword">struct</td>
 <td class="function_name"><a class="link" href="glib-The-Main-Event-Loop.html#GPollFD" title="struct GPollFD">GPollFD</a></td>
 </tr>
@@ -895,8 +899,8 @@ This is often used in GTK+ applications when showing modal dialog
 boxes. Note that event sources are associated with a particular
 <a class="link" href="glib-The-Main-Event-Loop.html#GMainContext" title="GMainContext"><span class="type">GMainContext</span></a>, and will be checked and dispatched for all main
 loops associated with that GMainContext.</p>
-<p>GTK+ contains wrappers of some of these functions, e.g. <code class="function">gtk_main()</code>,
-<code class="function">gtk_main_quit()</code> and <code class="function">gtk_events_pending()</code>.</p>
+<p>GTK+ contains wrappers of some of these functions, e.g. <a href="http://developer.gnome.org/gtk4/gtk4-General.html#gtk-main"><code class="function">gtk_main()</code></a>,
+<a href="http://developer.gnome.org/gtk4/gtk4-General.html#gtk-main-quit"><code class="function">gtk_main_quit()</code></a> and <a href="http://developer.gnome.org/gtk4/gtk4-General.html#gtk-events-pending"><code class="function">gtk_events_pending()</code></a>.</p>
 <div class="refsect3">
 <a name="id-1.4.2.6.9"></a><h4>Creating new source types</h4>
 <p>One of the unusual features of the <a class="link" href="glib-The-Main-Event-Loop.html#GMainLoop" title="GMainLoop"><span class="type">GMainLoop</span></a> functionality
@@ -2342,7 +2346,7 @@ these checks all over your code, since there are doubtless many,
 many things that the user could do. Instead, you can use the
 following techniques:</p>
 <div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem"><p>Use <code class="function">gtk_widget_set_sensitive()</code> or modal dialogs to prevent
+<li class="listitem"><p>Use <a href="http://developer.gnome.org/gtk4/GtkWidget.html#gtk-widget-set-sensitive"><code class="function">gtk_widget_set_sensitive()</code></a> or modal dialogs to prevent
 the user from interacting with elements while the main
 loop is recursing.</p></li>
 <li class="listitem"><p>Avoid main loop recursion in situations where you can't handle
@@ -2582,9 +2586,18 @@ the context used by functions like <a class="link" href="glib-The-Main-Event-Loo
 <p>Normally you would call this function shortly after creating a new
 thread, passing it a <a class="link" href="glib-The-Main-Event-Loop.html#GMainContext" title="GMainContext"><span class="type">GMainContext</span></a> which will be run by a
 <a class="link" href="glib-The-Main-Event-Loop.html#GMainLoop" title="GMainLoop"><span class="type">GMainLoop</span></a> in that thread, to set a new default context for all
-async operations in that thread. (In this case, you don't need to
-ever call <a class="link" href="glib-The-Main-Event-Loop.html#g-main-context-pop-thread-default" title="g_main_context_pop_thread_default ()"><code class="function">g_main_context_pop_thread_default()</code></a>.) In some cases
-however, you may want to schedule a single operation in a
+async operations in that thread. In this case you may not need to
+ever call <a class="link" href="glib-The-Main-Event-Loop.html#g-main-context-pop-thread-default" title="g_main_context_pop_thread_default ()"><code class="function">g_main_context_pop_thread_default()</code></a>, assuming you want the
+new <a class="link" href="glib-The-Main-Event-Loop.html#GMainContext" title="GMainContext"><span class="type">GMainContext</span></a> to be the default for the whole lifecycle of the
+thread.</p>
+<p>If you don't have control over how the new thread was created (e.g.
+in the new thread isn't newly created, or if the thread life
+cycle is managed by a <a class="link" href="glib-Thread-Pools.html#GThreadPool" title="struct GThreadPool"><span class="type">GThreadPool</span></a>), it is always suggested to wrap
+the logic that needs to use the new <a class="link" href="glib-The-Main-Event-Loop.html#GMainContext" title="GMainContext"><span class="type">GMainContext</span></a> inside a
+<a class="link" href="glib-The-Main-Event-Loop.html#g-main-context-push-thread-default" title="g_main_context_push_thread_default ()"><code class="function">g_main_context_push_thread_default()</code></a> / <a class="link" href="glib-The-Main-Event-Loop.html#g-main-context-pop-thread-default" title="g_main_context_pop_thread_default ()"><code class="function">g_main_context_pop_thread_default()</code></a>
+pair, otherwise threads that are re-used will end up never explicitly
+releasing the <a class="link" href="glib-The-Main-Event-Loop.html#GMainContext" title="GMainContext"><span class="type">GMainContext</span></a> reference they hold.</p>
+<p>In some cases you may want to schedule a single operation in a
 non-default context, or temporarily use a non-default context in
 the main thread. In that case, you can wrap the call to the
 asynchronous operation inside a
@@ -2594,7 +2607,7 @@ ensure that no other asynchronous operations accidentally get
 started while the non-default context is active.</p>
 <p>Beware that libraries that predate this function may not correctly
 handle being used from a thread with a thread-default context. Eg,
-see <a href="../GFile.html#g-file-supports-thread-contexts"><code class="function">g_file_supports_thread_contexts()</code></a>.</p>
+see <a href="https://developer.gnome.org/gio/unstable/GFile.html#g-file-supports-thread-contexts"><code class="function">g_file_supports_thread_contexts()</code></a>.</p>
 <div class="refsect3">
 <a name="g-main-context-push-thread-default.parameters"></a><h4>Parameters</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
@@ -3429,7 +3442,7 @@ if the call was interrupted.</p>
 <a name="GSourceDummyMarshal"></a><h3>GSourceDummyMarshal ()</h3>
 <pre class="programlisting"><span class="returnvalue">void</span>
 <span class="c_punctuation">(</span>*GSourceDummyMarshal<span class="c_punctuation">)</span> (<em class="parameter"><code><span class="type">void</span></code></em>);</pre>
-<p>This is just a placeholder for <a href="../gobject-Closures.html#GClosureMarshal"><span class="type">GClosureMarshal</span></a>,
+<p>This is just a placeholder for <a href="https://developer.gnome.org/gobject/unstable/gobject-Closures.html#GClosureMarshal"><span class="type">GClosureMarshal</span></a>,
 which cannot be used here for dependency reasons.</p>
 </div>
 <hr>
@@ -3666,10 +3679,10 @@ before the dispatch of your idle handler.</p>
 <span class="gtkdoc opt">{</span>
   SomeWidget <span class="gtkdoc opt">*</span>self <span class="gtkdoc opt">=</span> data<span class="gtkdoc opt">;</span>
    
-  <span class="function">GDK_THREADS_ENTER</span> <span class="gtkdoc opt">();</span>
+  <span class="function"><a href="http://developer.gnome.org/gdk3/gdk4-Threads.html#GDK-THREADS-ENTER:CAPS">GDK_THREADS_ENTER</a></span> <span class="gtkdoc opt">();</span>
   <span class="gtkdoc slc">// do stuff with self</span>
   self<span class="gtkdoc opt">-&gt;</span>idle_id <span class="gtkdoc opt">=</span> <span class="number">0</span><span class="gtkdoc opt">;</span>
-  <span class="function">GDK_THREADS_LEAVE</span> <span class="gtkdoc opt">();</span>
+  <span class="function"><a href="http://developer.gnome.org/gdk3/gdk4-Threads.html#GDK-THREADS-LEAVE:CAPS">GDK_THREADS_LEAVE</a></span> <span class="gtkdoc opt">();</span>
    
   <span class="keyword">return</span> G_SOURCE_REMOVE<span class="gtkdoc opt">;</span>
 <span class="gtkdoc opt">}</span>
@@ -3688,7 +3701,7 @@ before the dispatch of your idle handler.</p>
   <span class="keyword">if</span> <span class="gtkdoc opt">(</span>self<span class="gtkdoc opt">-&gt;</span>idle_id<span class="gtkdoc opt">)</span>
     <span class="function"><a href="glib-The-Main-Event-Loop.html#g-source-remove">g_source_remove</a></span> <span class="gtkdoc opt">(</span>self<span class="gtkdoc opt">-&gt;</span>idle_id<span class="gtkdoc opt">);</span>
    
-  <span class="function"><a href="../gobject-The-Base-Object-Type.html#G-OBJECT-CLASS:CAPS">G_OBJECT_CLASS</a></span> <span class="gtkdoc opt">(</span>parent_class<span class="gtkdoc opt">)-&gt;</span><span class="function">finalize</span> <span class="gtkdoc opt">(</span>object<span class="gtkdoc opt">);</span>
+  <span class="function"><a href="https://developer.gnome.org/gobject/unstable/gobject-The-Base-Object-Type.html#G-OBJECT-CLASS:CAPS">G_OBJECT_CLASS</a></span> <span class="gtkdoc opt">(</span>parent_class<span class="gtkdoc opt">)-&gt;</span><span class="function">finalize</span> <span class="gtkdoc opt">(</span>object<span class="gtkdoc opt">);</span>
 <span class="gtkdoc opt">}</span></pre></td>
       </tr>
     </tbody>
@@ -3724,12 +3737,12 @@ has already been destroy within the callback.</p>
 <span class="gtkdoc opt">{</span>
   SomeWidget <span class="gtkdoc opt">*</span>self <span class="gtkdoc opt">=</span> data<span class="gtkdoc opt">;</span>
   
-  <span class="function">GDK_THREADS_ENTER</span> <span class="gtkdoc opt">();</span>
+  <span class="function"><a href="http://developer.gnome.org/gdk3/gdk4-Threads.html#GDK-THREADS-ENTER:CAPS">GDK_THREADS_ENTER</a></span> <span class="gtkdoc opt">();</span>
   <span class="keyword">if</span> <span class="gtkdoc opt">(!</span><span class="function"><a href="glib-The-Main-Event-Loop.html#g-source-is-destroyed">g_source_is_destroyed</a></span> <span class="gtkdoc opt">(</span><span class="function"><a href="glib-The-Main-Event-Loop.html#g-main-current-source">g_main_current_source</a></span> <span class="gtkdoc opt">()))</span>
     <span class="gtkdoc opt">{</span>
       <span class="gtkdoc slc">// do stuff with self</span>
     <span class="gtkdoc opt">}</span>
-  <span class="function">GDK_THREADS_LEAVE</span> <span class="gtkdoc opt">();</span>
+  <span class="function"><a href="http://developer.gnome.org/gdk3/gdk4-Threads.html#GDK-THREADS-LEAVE:CAPS">GDK_THREADS_LEAVE</a></span> <span class="gtkdoc opt">();</span>
   
   <span class="keyword">return</span> FALSE<span class="gtkdoc opt">;</span>
 <span class="gtkdoc opt">}</span></pre></td>
@@ -4544,7 +4557,7 @@ callback), and when <em class="parameter"><code>source</code></em>
 its own prepare/check functions indicate that it is ready.)</p>
 <p>If you don't need <em class="parameter"><code>child_source</code></em>
  to do anything on its own when it
-triggers, you can call <a href="../gobject-Closures.html#g-source-set-dummy-callback"><code class="function">g_source_set_dummy_callback()</code></a> on it to set a
+triggers, you can call <a href="https://developer.gnome.org/gobject/unstable/gobject-Closures.html#g-source-set-dummy-callback"><code class="function">g_source_set_dummy_callback()</code></a> on it to set a
 callback that does nothing (except return <a class="link" href="glib-Standard-Macros.html#TRUE:CAPS" title="TRUE"><code class="literal">TRUE</code></a> if appropriate).</p>
 <p><em class="parameter"><code>source</code></em>
  will hold a reference on <em class="parameter"><code>child_source</code></em>
@@ -4882,6 +4895,15 @@ the g_spawn functions.</p>
 </div>
 <hr>
 <div class="refsect2">
+<a name="G-PID-FORMAT:CAPS"></a><h3>G_PID_FORMAT</h3>
+<pre class="programlisting">#define G_PID_FORMAT "i"
+</pre>
+<p>A format specifier that can be used in <code class="function">printf()</code>-style format strings
+when printing a <a class="link" href="glib-The-Main-Event-Loop.html#GPid" title="GPid"><span class="type">GPid</span></a>.</p>
+<p class="since">Since: <a class="link" href="api-index-2-50.html#api-index-2.50">2.50</a></p>
+</div>
+<hr>
+<div class="refsect2">
 <a name="GPollFD"></a><h3>struct GPollFD</h3>
 <pre class="programlisting">struct GPollFD {
 #if defined (G_OS_WIN32) &amp;&amp; GLIB_SIZEOF_VOID_P == 8

data/vendor/local/share/gtk-doc/html/glib/glib-Threads.html

@@ -607,18 +607,18 @@ you must coordinate accesses to the same <a class="link" href="glib-Hash-Tables.
 threads. The two notable exceptions from this rule are <a class="link" href="glib-The-Main-Event-Loop.html#GMainLoop" title="GMainLoop"><span class="type">GMainLoop</span></a>
 and <a class="link" href="glib-Asynchronous-Queues.html#GAsyncQueue" title="GAsyncQueue"><span class="type">GAsyncQueue</span></a>, which are thread-safe and need no further
 application-level locking to be accessed from multiple threads.
-Most refcounting functions such as <a href="../gobject-The-Base-Object-Type.html#g-object-ref"><code class="function">g_object_ref()</code></a> are also thread-safe.</p>
+Most refcounting functions such as <a href="https://developer.gnome.org/gobject/unstable/gobject-The-Base-Object-Type.html#g-object-ref"><code class="function">g_object_ref()</code></a> are also thread-safe.</p>
 <p>A common use for <a href="glib-Threads.html#GThread"><span class="type">GThreads</span></a> is to move a long-running blocking operation out
 of the main thread and into a worker thread. For GLib functions, such as
 single GIO operations, this is not necessary, and complicates the code.
 Instead, the <code class="literal">…<code class="function">_async()</code></code> version of the function should be used from the main
 thread, eliminating the need for locking and synchronisation between multiple
 threads. If an operation does need to be moved to a worker thread, consider
-using <a href="../GTask.html#g-task-run-in-thread"><code class="function">g_task_run_in_thread()</code></a>, or a <a class="link" href="glib-Thread-Pools.html#GThreadPool" title="struct GThreadPool"><span class="type">GThreadPool</span></a>. <a class="link" href="glib-Thread-Pools.html#GThreadPool" title="struct GThreadPool"><span class="type">GThreadPool</span></a> is often a
+using <a href="https://developer.gnome.org/gio/unstable/GTask.html#g-task-run-in-thread"><code class="function">g_task_run_in_thread()</code></a>, or a <a class="link" href="glib-Thread-Pools.html#GThreadPool" title="struct GThreadPool"><span class="type">GThreadPool</span></a>. <a class="link" href="glib-Thread-Pools.html#GThreadPool" title="struct GThreadPool"><span class="type">GThreadPool</span></a> is often a
 better choice than <a class="link" href="glib-Threads.html#GThread" title="GThread"><span class="type">GThread</span></a>, as it handles thread reuse and task queueing;
-<a href="../GTask.html#GTask-struct"><span class="type">GTask</span></a> uses this internally.</p>
+<a href="https://developer.gnome.org/gio/unstable/GTask.html#GTask-struct"><span class="type">GTask</span></a> uses this internally.</p>
 <p>However, if multiple blocking operations need to be performed in sequence,
-and it is not possible to use <a href="../GTask.html#GTask-struct"><span class="type">GTask</span></a> for them, moving them to a worker thread
+and it is not possible to use <a href="https://developer.gnome.org/gio/unstable/GTask.html#GTask-struct"><span class="type">GTask</span></a> for them, moving them to a worker thread
 can clarify the code.</p>
 </div>
 <div class="refsect1">

data/vendor/local/share/gtk-doc/html/glib/glib-UNIX-specific-utilities-and-integration.html

@@ -605,7 +605,7 @@ exported enumeration mapping <code class="literal">errno</code>. Instead, all fu
 error message is always generated via <a class="link" href="glib-String-Utility-Functions.html#g-strerror" title="g_strerror ()"><code class="function">g_strerror()</code></a>.</p>
 <p>It is expected that most code will not look at <code class="literal">errno</code> from these APIs.
 Important cases where one would want to differentiate between errors are
-already covered by existing cross-platform GLib API, such as e.g. <a href="../GFile.html#GFile-struct"><span class="type">GFile</span></a>
+already covered by existing cross-platform GLib API, such as e.g. <a href="https://developer.gnome.org/gio/unstable/GFile.html#GFile-struct"><span class="type">GFile</span></a>
 wrapping <code class="literal">ENOENT</code>. However, it is provided for completeness, at least.</p>
 </div>
 </div>

data/vendor/local/share/gtk-doc/html/glib/glib-URI-Functions.html

@@ -433,10 +433,10 @@ component following Section 3.3. of RFC 2396.</p>
 <tbody>
 <tr>
 <td class="parameter_name"><p>filename</p></td>
-<td class="parameter_description"><p>an absolute filename specified in the GLib file name encoding,
-which is the on-disk file name bytes on Unix, and UTF-8 on
-Windows</p></td>
-<td class="parameter_annotations"> </td>
+<td class="parameter_description"><p> an absolute filename specified in the GLib file
+name encoding, which is the on-disk file name bytes on Unix, and UTF-8
+on Windows. </p></td>
+<td class="parameter_annotations"><span class="annotation">[<acronym title="Override the parsed C type with given type."><span class="acronym">type</span></acronym> filename]</span></td>
 </tr>
 <tr>
 <td class="parameter_name"><p>hostname</p></td>

data/vendor/local/share/gtk-doc/html/glib/glib-Unicode-Manipulation.html

@@ -1555,7 +1555,7 @@ g_unichar_break_type (<em class="parameter"><code><a class="link" href="glib-Uni
 <a class="link" href="glib-Unicode-Manipulation.html#g-utf8-get-char" title="g_utf8_get_char ()"><code class="function">g_utf8_get_char()</code></a>). The break type is used to find word and line
 breaks ("text boundaries"), Pango implements the Unicode boundary
 resolution algorithms and normally you would use a function such
-as <code class="function">pango_break()</code> instead of caring about break types yourself.</p>
+as <a href="/home/mclasen/gnome/share/gtk-doc/html/pango/pango-Text-Processing.html#pango-break"><code class="function">pango_break()</code></a> instead of caring about break types yourself.</p>
 <div class="refsect3">
 <a name="g-unichar-break-type.parameters"></a><h4>Parameters</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
@@ -1736,7 +1736,7 @@ by Unicode Standard Annex #24). No check is made for <em class="parameter"><code
  being a
 valid Unicode character; if you pass in invalid character, the
 result is undefined.</p>
-<p>This function is equivalent to <code class="function">pango_script_for_unichar()</code> and the
+<p>This function is equivalent to <a href="/home/mclasen/gnome/share/gtk-doc/html/pango/pango-Scripts-and-Languages.html#pango-script-for-unichar"><code class="function">pango_script_for_unichar()</code></a> and the
 two are interchangeable.</p>
 <div class="refsect3">
 <a name="g-unichar-get-script.parameters"></a><h4>Parameters</h4>
@@ -3347,7 +3347,7 @@ To scan, use the format string "U+%06"G_GINT32_FORMAT"X".</p>
 2
 3</pre></td>
         <td class="listing_code"><pre class="programlisting">gunichar c<span class="gtkdoc opt">;</span>
-<span class="function">sscanf</span> <span class="gtkdoc opt">(</span><span class="string">&quot;U+0041&quot;</span><span class="gtkdoc opt">,</span> <span class="string">&quot;U+%06&quot;</span>G_GINT32_FORMAT<span class="string">&quot;X&quot;</span><span class="gtkdoc opt">, &amp;</span>c<span class="gtkdoc opt">)</span>
+<span class="function">sscanf</span> <span class="gtkdoc opt">(</span><span class="string">&quot;U+0041&quot;</span><span class="gtkdoc opt">,</span> <span class="string">&quot;U+%06&quot;</span>G_GINT32_FORMAT<span class="string">&quot;X&quot;</span><span class="gtkdoc opt">, &amp;</span>amp<span class="gtkdoc opt">;</span>c<span class="gtkdoc opt">)</span>
 <span class="function"><a href="glib-Warnings-and-Assertions.html#g-print">g_print</a></span> <span class="gtkdoc opt">(</span><span class="string">&quot;Read U+%04&quot;</span>G_GINT32_FORMAT<span class="string">&quot;X&quot;</span><span class="gtkdoc opt">,</span> c<span class="gtkdoc opt">);</span></pre></td>
       </tr>
     </tbody>
@@ -3387,7 +3387,7 @@ decomposition of a single Unicode character.</p>
 <a name="GUnicodeType"></a><h3>enum GUnicodeType</h3>
 <p>These are the possible character classifications from the
 Unicode specification.
-See &lt;ulink url="http://www.unicode.org/Public/UNIDATA/UnicodeData.html"&gt;http://www.unicode.org/Public/UNIDATA/UnicodeData.html&lt;/ulink&gt;.</p>
+See &lt;ulink url="http://www.unicode.org/reports/tr44/<span class="type">General_Category_Values</span>"&gt;Unicode Character Database&lt;/unlink&gt;.</p>
 <div class="refsect3">
 <a name="GUnicodeType.members"></a><h4>Members</h4>
 <div class="informaltable"><table class="informaltable" width="100%" border="0">
@@ -3918,6 +3918,27 @@ to handle unknown values. They may be regarded as <a class="link" href="glib-Uni
 </td>
 <td class="enum_member_annotations"> </td>
 </tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-BREAK-EMOJI-BASE:CAPS"></a>G_UNICODE_BREAK_EMOJI_BASE</p></td>
+<td class="enum_member_description">
+<p>Emoji Base (EB). Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-BREAK-EMOJI-MODIFIER:CAPS"></a>G_UNICODE_BREAK_EMOJI_MODIFIER</p></td>
+<td class="enum_member_description">
+<p>Emoji Modifier (EM). Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-BREAK-ZERO-WIDTH-JOINER:CAPS"></a>G_UNICODE_BREAK_ZERO_WIDTH_JOINER</p></td>
+<td class="enum_member_description">
+<p>Zero Width Joiner (ZWJ). Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
 </tbody>
 </table></div>
 </div>
@@ -3928,7 +3949,7 @@ to handle unknown values. They may be regarded as <a class="link" href="glib-Uni
 <p>The <a class="link" href="glib-Unicode-Manipulation.html#GUnicodeScript" title="enum GUnicodeScript"><span class="type">GUnicodeScript</span></a> enumeration identifies different writing
 systems. The values correspond to the names as defined in the
 Unicode standard. The enumeration has been added in GLib 2.14,
-and is interchangeable with <span class="type">PangoScript</span>.</p>
+and is interchangeable with <a href="/home/mclasen/gnome/share/gtk-doc/html/pango/pango-Scripts-and-Languages.html#PangoScript"><span class="type">PangoScript</span></a>.</p>
 <p>Note that new types may be added in the future. Applications
 should be ready to handle unknown values.
 See &lt;ulink
@@ -4875,6 +4896,48 @@ url="http://www.unicode.org/reports/tr24/"&gt;Unicode Standard Annex
 </td>
 <td class="enum_member_annotations"> </td>
 </tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-SCRIPT-ADLAM:CAPS"></a>G_UNICODE_SCRIPT_ADLAM</p></td>
+<td class="enum_member_description">
+<p>Adlam. Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-SCRIPT-BHAIKSUKI:CAPS"></a>G_UNICODE_SCRIPT_BHAIKSUKI</p></td>
+<td class="enum_member_description">
+<p>Bhaiksuki. Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-SCRIPT-MARCHEN:CAPS"></a>G_UNICODE_SCRIPT_MARCHEN</p></td>
+<td class="enum_member_description">
+<p>Marchen. Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-SCRIPT-NEWA:CAPS"></a>G_UNICODE_SCRIPT_NEWA</p></td>
+<td class="enum_member_description">
+<p>Newa. Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-SCRIPT-OSAGE:CAPS"></a>G_UNICODE_SCRIPT_OSAGE</p></td>
+<td class="enum_member_description">
+<p>Osage. Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
+<tr>
+<td class="enum_member_name"><p><a name="G-UNICODE-SCRIPT-TANGUT:CAPS"></a>G_UNICODE_SCRIPT_TANGUT</p></td>
+<td class="enum_member_description">
+<p>Tangut. Since: 2.50</p>
+</td>
+<td class="enum_member_annotations"> </td>
+</tr>
 </tbody>
 </table></div>
 </div>

data/vendor/local/share/gtk-doc/html/glib/glib-Version-Information.html

@@ -145,6 +145,10 @@
 </tr>
 <tr>
 <td class="define_keyword">#define</td>
+<td class="function_name"><a class="link" href="glib-Version-Information.html#GLIB-VERSION-2-50:CAPS" title="GLIB_VERSION_2_50">GLIB_VERSION_2_50</a></td>
+</tr>
+<tr>
+<td class="define_keyword">#define</td>
 <td class="function_name"><a class="link" href="glib-Version-Information.html#GLIB-VERSION-MIN-REQUIRED:CAPS" title="GLIB_VERSION_MIN_REQUIRED">GLIB_VERSION_MIN_REQUIRED</a></td>
 </tr>
 <tr>
@@ -341,20 +345,20 @@ linked against at application run time.</p>
 <hr>
 <div class="refsect2">
 <a name="GLIB-MINOR-VERSION:CAPS"></a><h3>GLIB_MINOR_VERSION</h3>
-<pre class="programlisting">#define GLIB_MINOR_VERSION 48
+<pre class="programlisting">#define GLIB_MINOR_VERSION 50
 </pre>
 <p>The minor version number of the GLib library.</p>
-<p>Like <span class="type">gtk_minor_version</span>, but from the headers used at
+<p>Like <a href="http://developer.gnome.org/gtk4/gtk4-Feature-Test-Macros.html#gtk-minor-version"><span class="type">gtk_minor_version</span></a>, but from the headers used at
 application compile time, rather than from the library
 linked against at application run time.</p>
 </div>
 <hr>
 <div class="refsect2">
 <a name="GLIB-MICRO-VERSION:CAPS"></a><h3>GLIB_MICRO_VERSION</h3>
-<pre class="programlisting">#define GLIB_MICRO_VERSION 1
+<pre class="programlisting">#define GLIB_MICRO_VERSION 2
 </pre>
 <p>The micro version number of the GLib library.</p>
-<p>Like <span class="type">gtk_micro_version</span>, but from the headers used at
+<p>Like <a href="http://developer.gnome.org/gtk4/gtk4-Feature-Test-Macros.html#gtk-micro-version"><span class="type">gtk_micro_version</span></a>, but from the headers used at
 application compile time, rather than from the library
 linked against at application run time.</p>
 </div>
@@ -468,6 +472,15 @@ that can be used by the C pre-processor.</p>
 </div>
 <hr>
 <div class="refsect2">
+<a name="GLIB-VERSION-2-50:CAPS"></a><h3>GLIB_VERSION_2_50</h3>
+<pre class="programlisting">#define GLIB_VERSION_2_50       (G_ENCODE_VERSION (2, 50))
+</pre>
+<p>A macro that evaluates to the 2.50 version of GLib, in a format
+that can be used by the C pre-processor.</p>
+<p class="since">Since: <a class="link" href="api-index-2-50.html#api-index-2.50">2.50</a></p>
+</div>
+<hr>
+<div class="refsect2">
 <a name="GLIB-VERSION-MIN-REQUIRED:CAPS"></a><h3>GLIB_VERSION_MIN_REQUIRED</h3>
 <pre class="programlisting"># define GLIB_VERSION_MIN_REQUIRED      (GLIB_VERSION_CUR_STABLE)
 </pre>