glib2 1.1.9-x86-mingw32 → 1.2.0-x86-mingw32

data/vendor/local/share/gtk-doc/html/gobject/ch01s02.html

@@ -21,7 +21,7 @@
 </tr></table>
 <div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="idp9152080"></a>Exporting a C API</h2></div></div></div>
+<a name="idp9959552"></a>Exporting a C API</h2></div></div></div>
 <p>
       C APIs are defined by a set of functions and global variables which are usually exported from a 
       binary. C functions have an arbitrary number of arguments and one return value. Each function is thus
@@ -91,7 +91,7 @@ call   0x80482f4 &lt;function_foo&gt;
         reads the original function signature.</p></li>
 <li class="listitem"><p>The solution used by GLib is to use the GType library which holds at runtime a description of
         all the objects manipulated by the programmer. This so-called <span class="emphasis"><em>dynamic type</em></span>
-        <a href="#ftn.idp9343056" class="footnote"><sup class="footnote"><a name="idp9343056"></a>[1]</sup></a>
+        <a href="#ftn.idp81488" class="footnote"><sup class="footnote"><a name="idp81488"></a>[1]</sup></a>
         library is then used by special generic glue code to automatically convert function parameters and
         function calling conventions between different runtime domains.</p></li>
 </ul></div>
@@ -100,7 +100,7 @@ call   0x80482f4 &lt;function_foo&gt;
       boundaries is written once: the figure below states this more clearly.
       </p>
 <div class="figure">
-<a name="idp132048"></a><p class="title"><b>Figure 1. </b></p>
+<a name="idp83488"></a><p class="title"><b>Figure 1. </b></p>
 <div class="figure-contents"><div class="mediaobject" align="center"><img src="glue.png" align="middle"></div></div>
 </div>
 <p><br class="figure-break">
@@ -118,7 +118,7 @@ call   0x80482f4 &lt;function_foo&gt;
     </p>
 <div class="footnotes">
 <br><hr style="width:100; align:left;">
-<div id="ftn.idp9343056" class="footnote"><p><a href="#idp9343056" class="para"><sup class="para">[1] </sup></a>
+<div id="ftn.idp81488" class="footnote"><p><a href="#idp81488" class="para"><sup class="para">[1] </sup></a>
             There are numerous different implementations of dynamic type systems: all C++ 
             compilers have one, Java and .NET have one too. A dynamic type system allows you
             to get information about every instantiated object at runtime. It can be implemented

data/vendor/local/share/gtk-doc/html/gobject/chapter-gtype.html

@@ -84,13 +84,13 @@ GType g_type_register_fundamental (GType                       type_id,
         <code class="function"><a class="link" href="gobject-Type-Information.html#g-type-register-fundamental" title="g_type_register_fundamental ()">g_type_register_fundamental</a></code> (you have to be Tim Janik 
         to do that) but in case you want to, the last chapter explains how to create
         new fundamental types.
-        <a href="#ftn.idp9135248" class="footnote"><sup class="footnote"><a name="idp9135248"></a>[2]</sup></a>
+        <a href="#ftn.idp9653792" class="footnote"><sup class="footnote"><a name="idp9653792"></a>[2]</sup></a>
       </p>
 <p>
         Fundamental types are top-level types which do not derive from any other type 
         while other non-fundamental types derive from other types.
-        Upon initialization, the type system not only initializes its
-        internal data structures but it also registers a number of core
+        Upon initialization by <code class="function"><a class="link" href="gobject-Type-Information.html#g-type-init" title="g_type_init ()">g_type_init</a></code>, the type system not 
+        only initializes its internal data structures but it also registers a number of core
         types: some of these are fundamental types. Others are types derived from these 
         fundamental types.
       </p>
@@ -248,7 +248,7 @@ struct _GTypeValueTable
 </div>
 <div class="footnotes">
 <br><hr style="width:100; align:left;">
-<div id="ftn.idp9135248" class="footnote"><p><a href="#idp9135248" class="para"><sup class="para">[2] </sup></a>
+<div id="ftn.idp9653792" class="footnote"><p><a href="#idp9653792" class="para"><sup class="para">[2] </sup></a>
             Please note that there exists another registration function: the 
             <code class="function"><a class="link" href="gobject-Type-Information.html#g-type-register-dynamic" title="g_type_register_dynamic ()">g_type_register_dynamic</a></code>. We will not discuss this
             function here since its use is very similar to the <code class="function">_static</code> 

data/vendor/local/share/gtk-doc/html/gobject/chapter-intro.html

@@ -23,7 +23,7 @@
 <div class="titlepage"><div><div><h2 class="title">
 <a name="chapter-intro"></a>Background</h2></div></div></div>
 <div class="toc"><dl>
-<dt><span class="sect1"><a href="chapter-intro.html#idp8363792">Data types and programming</a></span></dt>
+<dt><span class="sect1"><a href="chapter-intro.html#idp6962160">Data types and programming</a></span></dt>
 <dt><span class="sect1"><a href="ch01s02.html">Exporting a C API</a></span></dt>
 </dl></div>
 <p>
@@ -52,7 +52,7 @@
   </p>
 <div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="idp8363792"></a>Data types and programming</h2></div></div></div>
+<a name="idp6962160"></a>Data types and programming</h2></div></div></div>
 <p>
       One could say (I have seen such definitions used in some textbooks on programming language theory)
       that a programming language is merely a way to create data types and manipulate them. Most languages

data/vendor/local/share/gtk-doc/html/gobject/chapter-signal.html

@@ -25,8 +25,8 @@
 <div class="toc"><dl>
 <dt><span class="sect1"><a href="chapter-signal.html#closure">Closures</a></span></dt>
 <dd><dl>
-<dt><span class="sect2"><a href="chapter-signal.html#idp6266928">C Closures</a></span></dt>
-<dt><span class="sect2"><a href="chapter-signal.html#idp9657584">Non-C closures (for the fearless)</a></span></dt>
+<dt><span class="sect2"><a href="chapter-signal.html#idp11871888">C Closures</a></span></dt>
+<dt><span class="sect2"><a href="chapter-signal.html#idp7797968">Non-C closures (for the fearless)</a></span></dt>
 </dl></dd>
 <dt><span class="sect1"><a href="signal.html">Signals</a></span></dt>
 <dd><dl>
@@ -70,7 +70,7 @@ return_type function_callback (... , gpointer user_data);
       The <a class="link" href="gobject-Closures.html#GClosure" title="struct GClosure"><span class="type">GClosure</span></a> structure represents the common functionality of all
       closure implementations: there exists a different Closure implementation for
       each separate runtime which wants to use the GObject type system.
-      <a href="#ftn.idp11961824" class="footnote"><sup class="footnote"><a name="idp11961824"></a>[6]</sup></a>
+      <a href="#ftn.idp9564624" class="footnote"><sup class="footnote"><a name="idp9564624"></a>[6]</sup></a>
       The GObject library provides a simple <a class="link" href="gobject-Closures.html#GCClosure" title="struct GCClosure"><span class="type">GCClosure</span></a> type which
       is a specific implementation of closures to be used with C/C++ callbacks.
     </p>
@@ -93,13 +93,13 @@ return_type function_callback (... , gpointer user_data);
           events (<code class="function"><a class="link" href="gobject-Closures.html#g-closure-remove-finalize-notifier" title="g_closure_remove_finalize_notifier ()">g_closure_remove_finalize_notifier</a></code> and
           <code class="function"><a class="link" href="gobject-Closures.html#g-closure-remove-invalidate-notifier" title="g_closure_remove_invalidate_notifier ()">g_closure_remove_invalidate_notifier</a></code>) but not for the invocation 
           process.
-          <a href="#ftn.idp11552208" class="footnote"><sup class="footnote"><a name="idp11552208"></a>[7]</sup></a></p></li>
+          <a href="#ftn.idp11759824" class="footnote"><sup class="footnote"><a name="idp11759824"></a>[7]</sup></a></p></li>
 </ul></div>
 <p>
     </p>
 <div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp6266928"></a>C Closures</h3></div></div></div>
+<a name="idp11871888"></a>C Closures</h3></div></div></div>
 <p>
         If you are using C or C++
         to connect a callback to a given event, you will either use simple <a class="link" href="gobject-Closures.html#GCClosure" title="struct GCClosure"><span class="type">GCClosure</span></a>s
@@ -134,7 +134,7 @@ GClosure *g_signal_type_cclosure_new (GType          itype,
 </div>
 <div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp9657584"></a>Non-C closures (for the fearless)</h3></div></div></div>
+<a name="idp7797968"></a>Non-C closures (for the fearless)</h3></div></div></div>
 <p>
         As was explained above, closures hide the details of callback invocation. In C,
         callback invocation is just like function invocation: it is a matter of creating
@@ -193,7 +193,7 @@ g_cclosure_marshal_VOID__INT (GClosure     *closure,
 </div>
 <div class="footnotes">
 <br><hr style="width:100; align:left;">
-<div id="ftn.idp11961824" class="footnote"><p><a href="#idp11961824" class="para"><sup class="para">[6] </sup></a>
+<div id="ftn.idp9564624" class="footnote"><p><a href="#idp9564624" class="para"><sup class="para">[6] </sup></a>
         In practice, closures sit at the boundary of language runtimes: if you are
         writing Python code and one of your Python callbacks receives a signal from
         a GTK+ widget, the C code in GTK+ needs to execute your Python
@@ -201,7 +201,7 @@ g_cclosure_marshal_VOID__INT (GClosure     *closure,
         it behaves as a normal C object for GTK+ and as a normal Python object for
         Python code.
       </p></div>
-<div id="ftn.idp11552208" class="footnote"><p><a href="#idp11552208" class="para"><sup class="para">[7] </sup></a>
+<div id="ftn.idp11759824" class="footnote"><p><a href="#idp11759824" class="para"><sup class="para">[7] </sup></a>
             Closures are reference counted and notify listeners of their destruction in a two-stage
             process: the invalidation notifiers are invoked before the finalization notifiers.
           </p></div>

data/vendor/local/share/gtk-doc/html/gobject/glib-genmarshal.html

@@ -33,7 +33,7 @@
 <div class="cmdsynopsis"><p><code class="command">glib-genmarshal</code>  [OPTION...] [FILE...]</p></div>
 </div>
 <div class="refsect1">
-<a name="idp14413072"></a><h2>Description</h2>
+<a name="idp6641136"></a><h2>Description</h2>
 <p><span class="command"><strong>glib-genmarshal</strong></span> is a small utility that generates C code
 marshallers for callback functions of the GClosure mechanism in the GObject
 sublibrary of GLib. The marshaller functions have a standard signature,
@@ -48,7 +48,7 @@ input. The marshaller list is either read from standard input or from files
 passed as additional arguments on the command line.
 </p>
 <div class="refsect2">
-<a name="idp14499152"></a><h3>Marshaller list format</h3>
+<a name="idp6353456"></a><h3>Marshaller list format</h3>
 <p>
 The marshaller lists are processed line by line, a line can contain a
 comment in the form of
@@ -76,7 +76,7 @@ which are always pointers.
 </div>
 <hr>
 <div class="refsect2">
-<a name="idp139904"></a><h3>Parameter types</h3>
+<a name="idp4839200"></a><h3>Parameter types</h3>
 <p>
 Currently, the following types are supported:
 </p>
@@ -227,7 +227,7 @@ deprecated alias for <em class="replaceable"><code>BOOLEAN</code></em>
 </div>
 </div>
 <div class="refsect1">
-<a name="idp6717248"></a><h2>Options</h2>
+<a name="idp9900720"></a><h2>Options</h2>
 <div class="variablelist"><table border="0" class="variablelist">
 <colgroup>
 <col align="left" valign="top">
@@ -305,7 +305,7 @@ Print version and exit.
 </table></div>
 </div>
 <div class="refsect1">
-<a name="idp10643312"></a><h2>Example</h2>
+<a name="idp12559536"></a><h2>Example</h2>
 <p>
 To generate marshallers for the following callback functions:
 </p>
@@ -360,7 +360,7 @@ g_closure_set_marshal (cc_baz, g_cclosure_user_marshal_FLOAT__BOOLEAN_UCHAR);
 </pre>
 </div>
 <div class="refsect1">
-<a name="idp9686512"></a><h2>See also</h2>
+<a name="idp7264864"></a><h2>See also</h2>
 <p>
 <span class="citerefentry"><span class="refentrytitle">glib-mkenums</span>(1)</span>
 </p>

data/vendor/local/share/gtk-doc/html/gobject/glib-mkenums.html

@@ -33,7 +33,7 @@
 <div class="cmdsynopsis"><p><code class="command">glib-mkenums</code>  [OPTION...] [FILE...]</p></div>
 </div>
 <div class="refsect1">
-<a name="idp9836224"></a><h2>Description</h2>
+<a name="idp10503248"></a><h2>Description</h2>
 <p><span class="command"><strong>glib-mkenums</strong></span> is a small perl-script utility that
 parses C code to extract enum definitions and produces enum descriptions based
 on text templates specified by the user. Most frequently this script is used to
@@ -46,7 +46,7 @@ substitutions are performed on the text templates for keywords enclosed
 in @ characters.
 </p>
 <div class="refsect2">
-<a name="idp10104272"></a><h3>Production text substitutions</h3>
+<a name="idp7777392"></a><h3>Production text substitutions</h3>
 <p>
 Certain keywords enclosed in @ characters will be substituted in the
 emitted text. For the substitution examples of the keywords below,
@@ -163,7 +163,7 @@ The base name of the input file currently being processed (e.g. foo.h). (Since:
 </div>
 <hr>
 <div class="refsect2">
-<a name="idp4809264"></a><h3>Trigraph extensions</h3>
+<a name="idp13285888"></a><h3>Trigraph extensions</h3>
 <p>
 Some C comments are treated specially in the parsed enum definitions,
 such comments start out with the trigraph sequence <code class="literal">/*&lt;</code>
@@ -199,7 +199,7 @@ typedef enum /*&lt; flags,prefix=PREFIX &gt;*/
 </div>
 </div>
 <div class="refsect1">
-<a name="idp14335456"></a><h2>Options</h2>
+<a name="idp14613568"></a><h2>Options</h2>
 <div class="variablelist"><table border="0" class="variablelist">
 <colgroup>
 <col align="left" valign="top">
@@ -318,7 +318,7 @@ Print version and exit.
 </table></div>
 </div>
 <div class="refsect1">
-<a name="idp9650624"></a><h2>See also</h2>
+<a name="idp9466880"></a><h2>See also</h2>
 <p>
 <span class="citerefentry"><span class="refentrytitle">glib-genmarshal</span>(1)</span>
 </p>

data/vendor/local/share/gtk-doc/html/gobject/gobject-Boxed-Types.html

@@ -73,8 +73,6 @@
 #define             <a class="link" href="gobject-Boxed-Types.html#G-TYPE-MAIN-CONTEXT:CAPS" title="G_TYPE_MAIN_CONTEXT">G_TYPE_MAIN_CONTEXT</a>
 #define             <a class="link" href="gobject-Boxed-Types.html#G-TYPE-MAIN-LOOP:CAPS" title="G_TYPE_MAIN_LOOP">G_TYPE_MAIN_LOOP</a>
 #define             <a class="link" href="gobject-Boxed-Types.html#G-TYPE-SOURCE:CAPS" title="G_TYPE_SOURCE">G_TYPE_SOURCE</a>
-#define             <a class="link" href="gobject-Boxed-Types.html#G-TYPE-POLLFD:CAPS" title="G_TYPE_POLLFD">G_TYPE_POLLFD</a>
-#define             <a class="link" href="gobject-Boxed-Types.html#G-TYPE-THREAD:CAPS" title="G_TYPE_THREAD">G_TYPE_THREAD</a>
 typedef             <a class="link" href="gobject-Boxed-Types.html#GStrv" title="GStrv">GStrv</a>;
 </pre>
 </div>
@@ -507,26 +505,6 @@ The <a class="link" href="gobject-Type-Information.html#GType" title="GType"><sp
 </div>
 <hr>
 <div class="refsect2">
-<a name="G-TYPE-POLLFD:CAPS"></a><h3>G_TYPE_POLLFD</h3>
-<pre class="programlisting">#define G_TYPE_POLLFD (g_pollfd_get_type ())
-</pre>
-<p>
-The <a class="link" href="gobject-Type-Information.html#GType" title="GType"><span class="type">GType</span></a> for a boxed type holding a <a href="./../glib/glib/glib-The-Main-Event-Loop.html#GPollFD"><span class="type">GPollFD</span></a>.
-</p>
-<p class="since">Since 2.36</p>
-</div>
-<hr>
-<div class="refsect2">
-<a name="G-TYPE-THREAD:CAPS"></a><h3>G_TYPE_THREAD</h3>
-<pre class="programlisting">#define G_TYPE_THREAD (g_thread_get_type ())
-</pre>
-<p>
-The <a class="link" href="gobject-Type-Information.html#GType" title="GType"><span class="type">GType</span></a> for a boxed type holding a <a href="./../glib/glib/glib-Threads.html#GThread"><span class="type">GThread</span></a>.
-</p>
-<p class="since">Since 2.36</p>
-</div>
-<hr>
-<div class="refsect2">
 <a name="GStrv"></a><h3>GStrv</h3>
 <pre class="programlisting">typedef gchar** GStrv;
 </pre>

data/vendor/local/share/gtk-doc/html/gobject/gobject-Generic-values.html

@@ -152,7 +152,9 @@ features.
 49
 50
 51
-52</pre></td>
+52
+53
+54</pre></td>
         <td class="listing_code"><pre class="programlisting"><span class="preproc">#include</span><span class="normal"> </span><span class="string">&lt;glib-object.h&gt;</span>
 
 <span class="keyword">static</span><span class="normal"> </span><span class="type">void</span>
@@ -174,6 +176,8 @@ features.
 <span class="normal">  </span><span class="usertype">GValue</span><span class="normal"> b </span><span class="symbol">=</span><span class="normal"> <a href="gobject-Generic-values.html#G-VALUE-INIT:CAPS">G_VALUE_INIT</a></span><span class="symbol">;</span>
 <span class="normal">  </span><span class="keyword">const</span><span class="normal"> </span><span class="usertype">gchar</span><span class="normal"> </span><span class="symbol">*</span><span class="normal">message</span><span class="symbol">;</span>
 
+<span class="normal">  </span><span class="function"><a href="gobject-Type-Information.html#g-type-init">g_type_init</a></span><span class="normal"> </span><span class="symbol">();</span>
+
 <span class="normal">  </span><span class="comment">/* The GValue starts empty */</span>
 <span class="normal">  </span><span class="function"><a href="./../glib/glib/glib-Testing.html#g-assert">g_assert</a></span><span class="normal"> </span><span class="symbol">(!</span><span class="function"><a href="gobject-Standard-Parameter-and-Value-Types.html#G-VALUE-HOLDS-STRING:CAPS">G_VALUE_HOLDS_STRING</a></span><span class="normal"> </span><span class="symbol">(&amp;</span><span class="normal">a</span><span class="symbol">));</span>
 

data/vendor/local/share/gtk-doc/html/gobject/gobject-Signals.html

@@ -260,7 +260,7 @@ basically they are a per-type facility that is inherited.  A signal
 emission mainly involves invocation of a certain set of callbacks
 in precisely defined manner. There are two main categories of such
 callbacks, per-object 
-<a href="#ftn.idp21019008" class="footnote"><sup class="footnote"><a name="idp21019008"></a>[10]</sup></a>
+<a href="#ftn.idp21046352" class="footnote"><sup class="footnote"><a name="idp21046352"></a>[10]</sup></a>
 ones and user provided ones.
 The per-object callbacks are most often referred to as "object method
 handler" or "default (signal) handler", while user provided callbacks are
@@ -1448,10 +1448,36 @@ ensures that the <em class="parameter"><code>gobject</code></em> stays alive dur
 by temporarily adding a reference count to <em class="parameter"><code>gobject</code></em>.
 </p>
 <p>
-When the object is destroyed the signal handler will be automatically
-disconnected.  Note that this is not currently threadsafe (ie:
-emitting a signal while <em class="parameter"><code>gobject</code></em> is being destroyed in another thread
-is not safe).
+Note that there is a bug in GObject that makes this function
+much less useful than it might seem otherwise. Once <em class="parameter"><code>gobject</code></em> is
+disposed, the callback will no longer be called, but, the signal
+handler is <span class="emphasis"><em>not</em></span> currently disconnected. If the
+<em class="parameter"><code>instance</code></em> is itself being freed at the same time than this doesn't
+matter, since the signal will automatically be removed, but
+if <em class="parameter"><code>instance</code></em> persists, then the signal handler will leak. You
+should not remove the signal yourself because in a future versions of
+GObject, the handler <span class="emphasis"><em>will</em></span> automatically
+be disconnected.
+</p>
+<p>
+It's possible to work around this problem in a way that will
+continue to work with future versions of GObject by checking
+that the signal handler is still connected before disconnected it:
+</p>
+<div class="informalexample">
+  <table class="listing_frame" border="0" cellpadding="0" cellspacing="0">
+    <tbody>
+      <tr>
+        <td class="listing_lines" align="right"><pre>1
+2</pre></td>
+        <td class="listing_code"><pre class="programlisting"><span class="keyword">if</span><span class="normal"> </span><span class="symbol">(</span><span class="function"><a href="gobject-Signals.html#g-signal-handler-is-connected">g_signal_handler_is_connected</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">instance</span><span class="symbol">,</span><span class="normal"> id</span><span class="symbol">))</span>
+<span class="normal">  </span><span class="function"><a href="gobject-Signals.html#g-signal-handler-disconnect">g_signal_handler_disconnect</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">instance</span><span class="symbol">,</span><span class="normal"> id</span><span class="symbol">);</span></pre></td>
+      </tr>
+    </tbody>
+  </table>
+</div>
+
+<p>
 </p>
 <div class="variablelist"><table border="0" class="variablelist">
 <colgroup>
@@ -2791,7 +2817,7 @@ and no further handling is needed.
 </div>
 <div class="footnotes">
 <br><hr style="width:100; align:left;">
-<div id="ftn.idp21019008" class="footnote"><p><a href="#idp21019008" class="para"><sup class="para">[10] </sup></a>Although signals can deal with any kind of instantiatable 
+<div id="ftn.idp21046352" class="footnote"><p><a href="#idp21046352" class="para"><sup class="para">[10] </sup></a>Although signals can deal with any kind of instantiatable 
 type, i'm referring to those types as "object types" in the following, 
 simply because that is the context most users will encounter signals in.
 </p></div>

data/vendor/local/share/gtk-doc/html/gobject/gobject-The-Base-Object-Type.html

@@ -386,7 +386,7 @@ The class structure for the <span class="structname">GObject</span> type.
 <p>
 </p>
 <div class="example">
-<a name="idp14102032"></a><p class="title"><b>Example 1. Implementing singletons using a constructor</b></p>
+<a name="idp14115632"></a><p class="title"><b>Example 1. Implementing singletons using a constructor</b></p>
 <div class="example-contents">
   <table class="listing_frame" border="0" cellpadding="0" cellspacing="0">
     <tbody>
@@ -2128,7 +2128,7 @@ the type, for instance by calling <a href="./../glib/glib/glib-Memory-Allocation
 <p>
 </p>
 <div class="example">
-<a name="idp18033840"></a><p class="title"><b>Example 2. Using g_object_get()</b></p>
+<a name="idp18073840"></a><p class="title"><b>Example 2. Using g_object_get()</b></p>
 <div class="example-contents">
 An example of using <a class="link" href="gobject-The-Base-Object-Type.html#g-object-get" title="g_object_get ()"><code class="function">g_object_get()</code></a> to get the contents
 of three properties - one of type <a class="link" href="gobject-Type-Information.html#G-TYPE-INT:CAPS" title="G_TYPE_INT"><span class="type">G_TYPE_INT</span></a>,
@@ -2259,18 +2259,18 @@ instead, is to store the GParamSpec used with
 <span class="normal">  PROP_LAST</span>
 <span class="cbracket">}</span><span class="symbol">;</span>
 
-<span class="keyword">static</span><span class="normal"> </span><span class="usertype">GParamSpec</span><span class="normal"> </span><span class="symbol">*</span><span class="normal">properties</span><span class="symbol">[</span><span class="normal">PROP_LAST</span><span class="symbol">];</span>
+<span class="keyword">static</span><span class="normal"> </span><span class="usertype">GParamSpec</span><span class="normal"> </span><span class="symbol">*</span><span class="normal"><a href="/usr/share/gtk-doc/html/libbonobo/properties.html">properties</a></span><span class="symbol">[</span><span class="normal">PROP_LAST</span><span class="symbol">];</span>
 
 <span class="keyword">static</span><span class="normal"> </span><span class="type">void</span>
 <span class="function">my_object_class_init</span><span class="normal"> </span><span class="symbol">(</span><span class="usertype">MyObjectClass</span><span class="normal"> </span><span class="symbol">*</span><span class="normal">klass</span><span class="symbol">)</span>
 <span class="cbracket">{</span>
-<span class="normal">  properties</span><span class="symbol">[</span><span class="normal">PROP_FOO</span><span class="symbol">]</span><span class="normal"> </span><span class="symbol">=</span><span class="normal"> </span><span class="function"><a href="gobject-Standard-Parameter-and-Value-Types.html#g-param-spec-int">g_param_spec_int</a></span><span class="normal"> </span><span class="symbol">(</span><span class="string">"foo"</span><span class="symbol">,</span><span class="normal"> </span><span class="string">"Foo"</span><span class="symbol">,</span><span class="normal"> </span><span class="string">"The foo"</span><span class="symbol">,</span>
+<span class="normal">  <a href="/usr/share/gtk-doc/html/libbonobo/properties.html">properties</a></span><span class="symbol">[</span><span class="normal">PROP_FOO</span><span class="symbol">]</span><span class="normal"> </span><span class="symbol">=</span><span class="normal"> </span><span class="function"><a href="gobject-Standard-Parameter-and-Value-Types.html#g-param-spec-int">g_param_spec_int</a></span><span class="normal"> </span><span class="symbol">(</span><span class="string">"foo"</span><span class="symbol">,</span><span class="normal"> </span><span class="string">"Foo"</span><span class="symbol">,</span><span class="normal"> </span><span class="string">"The foo"</span><span class="symbol">,</span>
 <span class="normal">                                           </span><span class="number">0</span><span class="symbol">,</span><span class="normal"> </span><span class="number">100</span><span class="symbol">,</span>
 <span class="normal">                                           </span><span class="number">50</span><span class="symbol">,</span>
 <span class="normal">                                           <a href="gobject-GParamSpec.html#G-PARAM-READWRITE:CAPS">G_PARAM_READWRITE</a></span><span class="symbol">);</span>
 <span class="normal">  </span><span class="function"><a href="gobject-The-Base-Object-Type.html#g-object-class-install-property">g_object_class_install_property</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">gobject_class</span><span class="symbol">,</span>
 <span class="normal">                                   PROP_FOO</span><span class="symbol">,</span>
-<span class="normal">                                   properties</span><span class="symbol">[</span><span class="normal">PROP_FOO</span><span class="symbol">]);</span>
+<span class="normal">                                   <a href="/usr/share/gtk-doc/html/libbonobo/properties.html">properties</a></span><span class="symbol">[</span><span class="normal">PROP_FOO</span><span class="symbol">]);</span>
 <span class="cbracket">}</span></pre></td>
       </tr>
     </tbody>
@@ -2289,7 +2289,7 @@ and then notify a change on the "foo" property with:
     <tbody>
       <tr>
         <td class="listing_lines" align="right"><pre>1</pre></td>
-        <td class="listing_code"><pre class="programlisting"><span class="function"><a href="gobject-The-Base-Object-Type.html#g-object-notify-by-pspec">g_object_notify_by_pspec</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">self</span><span class="symbol">,</span><span class="normal"> properties</span><span class="symbol">[</span><span class="normal">PROP_FOO</span><span class="symbol">]);</span></pre></td>
+        <td class="listing_code"><pre class="programlisting"><span class="function"><a href="gobject-The-Base-Object-Type.html#g-object-notify-by-pspec">g_object_notify_by_pspec</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">self</span><span class="symbol">,</span><span class="normal"> <a href="/usr/share/gtk-doc/html/libbonobo/properties.html">properties</a></span><span class="symbol">[</span><span class="normal">PROP_FOO</span><span class="symbol">]);</span></pre></td>
       </tr>
     </tbody>
   </table>

data/vendor/local/share/gtk-doc/html/gobject/gobject-Type-Information.html

@@ -197,7 +197,6 @@ enum                <a class="link" href="gobject-Type-Information.html#GTypeFun
                                                          <em class="parameter"><code><a href="./../glib/glib/glib-Basic-Types.html#gpointer"><span class="type">gpointer</span></a> g_iface</code></em>);
 <a class="link" href="gobject-Type-Information.html#GTypeValueTable" title="struct GTypeValueTable"><span class="returnvalue">GTypeValueTable</span></a> *   <a class="link" href="gobject-Type-Information.html#g-type-value-table-peek" title="g_type_value_table_peek ()">g_type_value_table_peek</a>             (<em class="parameter"><code><a class="link" href="gobject-Type-Information.html#GType" title="GType"><span class="type">GType</span></a> type</code></em>);
 <span class="returnvalue">void</span>                <a class="link" href="gobject-Type-Information.html#g-type-ensure" title="g_type_ensure ()">g_type_ensure</a>                       (<em class="parameter"><code><a class="link" href="gobject-Type-Information.html#GType" title="GType"><span class="type">GType</span></a> type</code></em>);
-<a href="./../glib/glib/glib-Basic-Types.html#guint"><span class="returnvalue">guint</span></a>               <a class="link" href="gobject-Type-Information.html#g-type-get-type-registration-serial" title="g_type_get_type_registration_serial ()">g_type_get_type_registration_serial</a> (<em class="parameter"><code><span class="type">void</span></code></em>);
 #define             <a class="link" href="gobject-Type-Information.html#G-DEFINE-TYPE:CAPS" title="G_DEFINE_TYPE()">G_DEFINE_TYPE</a>                       (TN,
                                                          t_n,
                                                          T_P)
@@ -278,7 +277,9 @@ enum                <a class="link" href="gobject-Type-Information.html#GTypeFun
 <p>
 The GType API is the foundation of the GObject system.  It provides the
 facilities for registering and managing all fundamental data types,
-user-defined object and interface types.
+user-defined object and interface types.  Before using any GType
+or GObject functions, <a class="link" href="gobject-Type-Information.html#g-type-init" title="g_type_init ()"><code class="function">g_type_init()</code></a> must be called to initialize the
+type system.
 </p>
 <p>
 For type creation and registration purposes, all types fall into one of
@@ -1665,14 +1666,21 @@ A bit in the type number that's supposed to be left untouched.
 <div class="refsect2">
 <a name="g-type-init"></a><h3>g_type_init ()</h3>
 <pre class="programlisting"><span class="returnvalue">void</span>                g_type_init                         (<em class="parameter"><code><span class="type">void</span></code></em>);</pre>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
-<h3 class="title">Warning</h3>
-<p><code class="literal">g_type_init</code> has been deprecated since version 2.36 and should not be used in newly-written code. the type system is now initialised automatically</p>
-</div>
 <p>
-This function used to initialise the type system.  Since GLib 2.36,
-the type system is initialised automatically and this function does
-nothing.
+Prior to any use of the type system, <a class="link" href="gobject-Type-Information.html#g-type-init" title="g_type_init ()"><code class="function">g_type_init()</code></a> has to be called
+to initialize the type system and assorted other code portions
+(such as the various fundamental type implementations or the signal
+system).
+</p>
+<p>
+This function is idempotent: If you call it multiple times, all but
+the first calls will be silently ignored.
+</p>
+<p>
+There is no way to undo the effect of <a class="link" href="gobject-Type-Information.html#g-type-init" title="g_type_init ()"><code class="function">g_type_init()</code></a>.
+</p>
+<p>
+Since version 2.24 this also initializes the thread system
 </p>
 </div>
 <hr>
@@ -1685,17 +1693,12 @@ nothing.
   G_TYPE_DEBUG_MASK = 0x03
 } GTypeDebugFlags;
 </pre>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
-<h3 class="title">Warning</h3>
-<p><code class="literal">GTypeDebugFlags</code> has been deprecated since version 2.36 and should not be used in newly-written code. <a class="link" href="gobject-Type-Information.html#g-type-init" title="g_type_init ()"><code class="function">g_type_init()</code></a> is now done automatically</p>
-</div>
-<p>
-These flags used to be passed to <a class="link" href="gobject-Type-Information.html#g-type-init-with-debug-flags" title="g_type_init_with_debug_flags ()"><code class="function">g_type_init_with_debug_flags()</code></a> which
-is now deprecated.
-</p>
 <p>
-If you need to enable debugging features, use the GOBJECT_DEBUG
-environment variable.
+The <span class="type">GTypeDebugFlags</span> enumeration values can be passed to
+<a class="link" href="gobject-Type-Information.html#g-type-init-with-debug-flags" title="g_type_init_with_debug_flags ()"><code class="function">g_type_init_with_debug_flags()</code></a> to trigger debugging messages during runtime.
+Note that the messages can also be triggered by setting the
+<code class="envar">GOBJECT_DEBUG</code> environment variable to a ':'-separated list of 
+"objects" and "signals".
 </p>
 <div class="variablelist"><table border="0" class="variablelist">
 <colgroup>
@@ -1730,18 +1733,11 @@ environment variable.
 <div class="refsect2">
 <a name="g-type-init-with-debug-flags"></a><h3>g_type_init_with_debug_flags ()</h3>
 <pre class="programlisting"><span class="returnvalue">void</span>                g_type_init_with_debug_flags        (<em class="parameter"><code><a class="link" href="gobject-Type-Information.html#GTypeDebugFlags" title="enum GTypeDebugFlags"><span class="type">GTypeDebugFlags</span></a> debug_flags</code></em>);</pre>
-<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
-<h3 class="title">Warning</h3>
-<p><code class="literal">g_type_init_with_debug_flags</code> has been deprecated since version 2.36 and should not be used in newly-written code. the type system is now initialised automatically</p>
-</div>
 <p>
-This function used to initialise the type system with debugging
-flags.  Since GLib 2.36, the type system is initialised automatically
-and this function does nothing.
+Similar to <a class="link" href="gobject-Type-Information.html#g-type-init" title="g_type_init ()"><code class="function">g_type_init()</code></a>, but additionally sets debug flags.
 </p>
 <p>
-If you need to enable debugging features, use the GOBJECT_DEBUG
-environment variable.
+This function is idempotent.
 </p>
 <div class="variablelist"><table border="0" class="variablelist">
 <colgroup>
@@ -3830,29 +3826,6 @@ type's <code class="function">_get_type()</code> method is called.
 </div>
 <hr>
 <div class="refsect2">
-<a name="g-type-get-type-registration-serial"></a><h3>g_type_get_type_registration_serial ()</h3>
-<pre class="programlisting"><a href="./../glib/glib/glib-Basic-Types.html#guint"><span class="returnvalue">guint</span></a>               g_type_get_type_registration_serial (<em class="parameter"><code><span class="type">void</span></code></em>);</pre>
-<p>
-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.
-</p>
-<div class="variablelist"><table border="0" class="variablelist">
-<colgroup>
-<col align="left" valign="top">
-<col>
-</colgroup>
-<tbody><tr>
-<td><p><span class="term"><span class="emphasis"><em>Returns</em></span> :</span></p></td>
-<td>An unsigned int, representing the state of type registrations.</td>
-</tr></tbody>
-</table></div>
-<p class="since">Since 2.36</p>
-</div>
-<hr>
-<div class="refsect2">
 <a name="G-DEFINE-TYPE:CAPS"></a><h3>G_DEFINE_TYPE()</h3>
 <pre class="programlisting">#define G_DEFINE_TYPE(TN, t_n, T_P)			    G_DEFINE_TYPE_EXTENDED (TN, t_n, T_P, 0, {})
 </pre>