RubyGems - glib2 - Versions diffs - 0.90.8-x86-mingw32 → 0.90.9-x86-mingw32 - Mend

glib2 0.90.8-x86-mingw32 → 0.90.9-x86-mingw32

Files changed (620) hide show

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

@@ -8,7 +8,7 @@
 <link rel="up" href="chapter-intro.html" title="Background">
 <link rel="prev" href="chapter-intro.html" title="Background">
 <link rel="next" href="chapter-gtype.html" title="The GLib Dynamic Type System">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,9 +19,9 @@
 <th width="100%" align="center">GObject Reference Manual</th>
 <td><a accesskey="n" href="chapter-gtype.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="sect1" title="Exporting a C API">
+<div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id363501"></a>Exporting a C API</h2></div></div></div>
+<a name="id570612"></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>
-        <sup>[<a name="id296325" href="#ftn.id296325" class="footnote">1</a>]</sup>
+        <sup>[<a name="id503415" href="#ftn.id503415" class="footnote">1</a>]</sup>
         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="id296342"></a><p class="title"><b>Figure 1. </b></p>
+<a name="id503434"></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 width="100" align="left">
-<div class="footnote"><p><sup>[<a id="ftn.id296325" href="#id296325" class="para">1</a>] </sup>
+<div class="footnote"><p><sup>[<a id="ftn.id503415" href="#id503415" class="para">1</a>] </sup>
             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
@@ -131,6 +131,6 @@ call   0x80482f4 &lt;function_foo&gt;
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gobject/ch06s03.html CHANGED

@@ -8,7 +8,7 @@
 <link rel="up" href="howto-interface.html" title="How to define and implement interfaces">
 <link rel="prev" href="howto-interface-implement.html" title="How To define implement an Interface?">
 <link rel="next" href="howto-interface-properties.html" title="Interface Properties">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,9 +19,9 @@
 <th width="100%" align="center">GObject Reference Manual</th>
 <td><a accesskey="n" href="howto-interface-properties.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="sect1" title="Interface definition prerequisites">
+<div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id442160"></a>Interface definition prerequisites</h2></div></div></div>
+<a name="id652050"></a>Interface definition prerequisites</h2></div></div></div>
 <p>
       To specify that an interface requires the presence of other interfaces
       when implemented, GObject introduces the concept of
@@ -108,6 +108,6 @@ G_DEFINE_TYPE_WITH_CODE (MamanBar, maman_bar, G_TYPE_OBJECT,
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="pt01.html" title="Part I. Concepts">
 <link rel="prev" href="gtype-non-instantiable-classed.html" title="Non-instantiable classed types: interfaces">
 <link rel="next" href="gobject-memory.html" title="Object memory management">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GObject Reference Manual</th>
 <td><a accesskey="n" href="gobject-memory.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="chapter" title="The GObject base class">
+<div class="chapter">
 <div class="titlepage"><div><div><h2 class="title">
 <a name="chapter-gobject"></a>The GObject base class</h2></div></div></div>
 <div class="toc"><dl>
@@ -36,10 +36,10 @@
 <p>
     The two previous chapters discussed the details of GLib's Dynamic Type System
     and its signal control system. The GObject library also contains an implementation
-    for a base fundamental type named <span class="type"><a class="link" href="gobject-The-Base-Object-Type.html#GObject">GObject</a></span>.
+    for a base fundamental type named <a class="link" href="gobject-The-Base-Object-Type.html#GObject"><span class="type">GObject</span></a>.
   </p>
 <p>
-    <span class="type"><a class="link" href="gobject-The-Base-Object-Type.html#GObject">GObject</a></span> is a fundamental classed instantiable type. It implements:
+    <a class="link" href="gobject-The-Base-Object-Type.html#GObject"><span class="type">GObject</span></a> is a fundamental classed instantiable type. It implements:
     </p>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc">
 <li class="listitem"><p>Memory management with reference counting</p></li>
@@ -49,10 +49,10 @@
 </ul></div>
 <p>
     All the GNOME libraries which use the GLib type system (like GTK+ and GStreamer)
-    inherit from <span class="type"><a class="link" href="gobject-The-Base-Object-Type.html#GObject">GObject</a></span> which is why it is important to understand
+    inherit from <a class="link" href="gobject-The-Base-Object-Type.html#GObject"><span class="type">GObject</span></a> which is why it is important to understand
     the details of how it works.
   </p>
-<div class="sect1" title="Object instantiation">
+<div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="gobject-instantiation"></a>Object instantiation</h2></div></div></div>
 <p>
@@ -128,10 +128,7 @@ maman_bar_constructor (GType                  gtype,
   {
     /* Always chain up to the parent constructor */
-    MamanBarClass *klass;
-    GObjectClass *parent_class;
-    parent_class = G_OBJECT_CLASS (maman_bar_parent_class);
-    obj = parent_class-&gt;constructor (gtype, n_properties, properties);
+    obj = G_OBJECT_CLASS (maman_bar_parent_class)-&gt;constructor (gtype, n_properties, properties);
   }
   /* update the object state depending on constructor properties */
@@ -288,6 +285,6 @@ MamanBar *bar = g_object_new (MAMAN_TYPE_BAR, NULL);
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="pt01.html" title="Part I. Concepts">
 <link rel="prev" href="ch01s02.html" title="Exporting a C API">
 <link rel="next" href="gtype-conventions.html" title="Conventions">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GObject Reference Manual</th>
 <td><a accesskey="n" href="gtype-conventions.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="chapter" title="The GLib Dynamic Type System">
+<div class="chapter">
 <div class="titlepage"><div><div><h2 class="title">
 <a name="chapter-gtype"></a>The GLib Dynamic Type System</h2></div></div></div>
 <div class="toc"><dl>
@@ -79,12 +79,12 @@ 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>
         are the C functions, defined in
         <code class="filename">gtype.h</code> and implemented in <code class="filename">gtype.c</code>
-        which you should use to register a new <span class="type"><a class="link" href="gobject-Type-Information.html#GType" title="GType">GType</a></span> in the program's type system.
+        which you should use to register a new <a class="link" href="gobject-Type-Information.html#GType" title="GType"><span class="type">GType</span></a> in the program's type system.
         It is not likely you will ever need to use
         <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.
-        <sup>[<a name="id340555" href="#ftn.id340555" class="footnote">2</a>]</sup>
+        <sup>[<a name="id547823" href="#ftn.id547823" class="footnote">2</a>]</sup>
       </p>
 <p>
         Fundamental types are top-level types which do not derive from any other type
@@ -99,40 +99,40 @@ GType g_type_register_fundamental (GType                       type_id,
         </p>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc">
 <li class="listitem"><p>
-            class size: the class_size field in <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeInfo" title="GTypeInfo">GTypeInfo</a></span>.
+            class size: the class_size field in <a class="link" href="gobject-Type-Information.html#GTypeInfo" title="struct GTypeInfo"><span class="type">GTypeInfo</span></a>.
           </p></li>
 <li class="listitem"><p>
             class initialization functions (C++ constructor): the base_init and
-            class_init fields in <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeInfo" title="GTypeInfo">GTypeInfo</a></span>.
+            class_init fields in <a class="link" href="gobject-Type-Information.html#GTypeInfo" title="struct GTypeInfo"><span class="type">GTypeInfo</span></a>.
           </p></li>
 <li class="listitem"><p>
             class destruction functions (C++ destructor): the base_finalize and
-            class_finalize fields in <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeInfo" title="GTypeInfo">GTypeInfo</a></span>.
+            class_finalize fields in <a class="link" href="gobject-Type-Information.html#GTypeInfo" title="struct GTypeInfo"><span class="type">GTypeInfo</span></a>.
           </p></li>
 <li class="listitem"><p>
             instance size (C++ parameter to new): the instance_size field in
-            <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeInfo" title="GTypeInfo">GTypeInfo</a></span>.
+            <a class="link" href="gobject-Type-Information.html#GTypeInfo" title="struct GTypeInfo"><span class="type">GTypeInfo</span></a>.
           </p></li>
 <li class="listitem"><p>
             instantiation policy (C++ type of new operator): the n_preallocs
-            field in <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeInfo" title="GTypeInfo">GTypeInfo</a></span>.
+            field in <a class="link" href="gobject-Type-Information.html#GTypeInfo" title="struct GTypeInfo"><span class="type">GTypeInfo</span></a>.
           </p></li>
 <li class="listitem"><p>
             copy functions (C++ copy operators): the value_table field in
-            <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeInfo" title="GTypeInfo">GTypeInfo</a></span>.
+            <a class="link" href="gobject-Type-Information.html#GTypeInfo" title="struct GTypeInfo"><span class="type">GTypeInfo</span></a>.
           </p></li>
 <li class="listitem"><p>
-            type characteristic flags: <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeFlags" title="enum GTypeFlags">GTypeFlags</a></span>.
+            type characteristic flags: <a class="link" href="gobject-Type-Information.html#GTypeFlags" title="enum GTypeFlags"><span class="type">GTypeFlags</span></a>.
           </p></li>
 </ul></div>
 <p>
-        Fundamental types are also defined by a set of <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeFundamentalFlags" title="enum GTypeFundamentalFlags">GTypeFundamentalFlags</a></span>
-        which are stored in a <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeFundamentalInfo" title="GTypeFundamentalInfo">GTypeFundamentalInfo</a></span>.
+        Fundamental types are also defined by a set of <a class="link" href="gobject-Type-Information.html#GTypeFundamentalFlags" title="enum GTypeFundamentalFlags"><span class="type">GTypeFundamentalFlags</span></a>
+        which are stored in a <a class="link" href="gobject-Type-Information.html#GTypeFundamentalInfo" title="struct GTypeFundamentalInfo"><span class="type">GTypeFundamentalInfo</span></a>.
         Non-fundamental types are furthermore defined by the type of their parent which is
         passed as the parent_type parameter to <code class="function"><a class="link" href="gobject-Type-Information.html#g-type-register-static" title="g_type_register_static ()">g_type_register_static</a></code>
         and <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>.
       </p>
-<div class="sect1" title="Copy functions">
+<div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="gtype-copy"></a>Copy functions</h2></div></div></div>
 <p>
@@ -141,16 +141,16 @@ GType g_type_register_fundamental (GType                       type_id,
           they can all be manipulated through a single API to copy/assign them.
         </p>
 <p>
-          The <span class="type"><a class="link" href="gobject-Generic-values.html#GValue" title="GValue">GValue</a></span> structure is used as an abstract container for all of these
+          The <a class="link" href="gobject-Generic-values.html#GValue" title="GValue"><span class="type">GValue</span></a> structure is used as an abstract container for all of these
           types. Its simplistic API (defined in <code class="filename">gobject/gvalue.h</code>) can be
           used to invoke the value_table functions registered
           during type registration: for example <code class="function"><a class="link" href="gobject-Generic-values.html#g-value-copy" title="g_value_copy ()">g_value_copy</a></code> copies the
-          content of a <span class="type"><a class="link" href="gobject-Generic-values.html#GValue" title="GValue">GValue</a></span> to another <span class="type"><a class="link" href="gobject-Generic-values.html#GValue" title="GValue">GValue</a></span>. This is similar
+          content of a <a class="link" href="gobject-Generic-values.html#GValue" title="GValue"><span class="type">GValue</span></a> to another <a class="link" href="gobject-Generic-values.html#GValue" title="GValue"><span class="type">GValue</span></a>. This is similar
           to a C++ assignment which invokes the C++ copy operator to modify the default
           bit-by-bit copy semantics of C++/C structures/classes.
         </p>
 <p>
-          The following code shows how you can copy around a 64 bit integer, as well as a <span class="type"><a class="link" href="gobject-The-Base-Object-Type.html#GObject">GObject</a></span>
+          The following code shows how you can copy around a 64 bit integer, as well as a <a class="link" href="gobject-The-Base-Object-Type.html#GObject"><span class="type">GObject</span></a>
           instance pointer (sample code for this is located in the source tarball for this document in
           <code class="filename">sample/gtype/test.c</code>):
 </p>
@@ -248,7 +248,7 @@ struct _GTypeValueTable
 </div>
 <div class="footnotes">
 <br><hr width="100" align="left">
-<div class="footnote"><p><sup>[<a id="ftn.id340555" href="#id340555" class="para">2</a>] </sup>
+<div class="footnote"><p><sup>[<a id="ftn.id547823" href="#id547823" class="para">2</a>] </sup>
             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>
@@ -258,6 +258,6 @@ struct _GTypeValueTable
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="pt01.html" title="Part I. Concepts">
 <link rel="prev" href="pt01.html" title="Part I. Concepts">
 <link rel="next" href="ch01s02.html" title="Exporting a C API">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,11 +19,11 @@
 <th width="100%" align="center">GObject Reference Manual</th>
 <td><a accesskey="n" href="ch01s02.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="chapter" title="Background">
+<div class="chapter">
 <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#id350436">Data types and programming</a></span></dt>
+<dt><span class="sect1"><a href="chapter-intro.html#id557547">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>
@@ -50,9 +50,9 @@
     goals: this can often explain the sometimes rather convoluted APIs and features present
     in this library.
   </p>
-<div class="sect1" title="Data types and programming">
+<div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id350436"></a>Data types and programming</h2></div></div></div>
+<a name="id557547"></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
@@ -87,6 +87,6 @@ print "this is an integer converted to a string:" . $tmp . "\n";
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="pt01.html" title="Part I. Concepts">
 <link rel="prev" href="gobject-properties.html" title="Object properties">
 <link rel="next" href="signal.html" title="Signals">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,14 +19,14 @@
 <th width="100%" align="center">GObject Reference Manual</th>
 <td><a accesskey="n" href="signal.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div class="chapter" title="The GObject messaging system">
+<div class="chapter">
 <div class="titlepage"><div><div><h2 class="title">
 <a name="chapter-signal"></a>The GObject messaging system</h2></div></div></div>
 <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#id337933">C Closures</a></span></dt>
-<dt><span class="sect2"><a href="chapter-signal.html#id362303">Non-C closures (for the fearless)</a></span></dt>
+<dt><span class="sect2"><a href="chapter-signal.html#id567477">C Closures</a></span></dt>
+<dt><span class="sect2"><a href="chapter-signal.html#id576670">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>
@@ -36,7 +36,7 @@
 <dt><span class="sect2"><a href="signal.html#signal-detail">The <span class="emphasis"><em>detail</em></span> argument</a></span></dt>
 </dl></dd>
 </dl></div>
-<div class="sect1" title="Closures">
+<div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="closure"></a>Closures</h2></div></div></div>
 <p>
@@ -67,15 +67,15 @@ return_type function_callback (... , gpointer user_data);
 <p>
     </p>
 <p>
-      The <span class="type"><a class="link" href="gobject-Closures.html#GClosure" title="GClosure">GClosure</a></span> structure represents the common functionality of all
+      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.
-      <sup>[<a name="id342247" href="#ftn.id342247" class="footnote">6</a>]</sup>
-      The GObject library provides a simple <span class="type"><a class="link" href="gobject-Closures.html#GCClosure" title="GCClosure">GCClosure</a></span> type which
+      <sup>[<a name="id545371" href="#ftn.id545371" class="footnote">6</a>]</sup>
+      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>
 <p>
-      A <span class="type"><a class="link" href="gobject-Closures.html#GClosure" title="GClosure">GClosure</a></span> provides simple services:
+      A <a class="link" href="gobject-Closures.html#GClosure" title="struct GClosure"><span class="type">GClosure</span></a> provides simple services:
       </p>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc">
 <li class="listitem"><p>
@@ -93,16 +93,16 @@ 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.
-          <sup>[<a name="id337923" href="#ftn.id337923" class="footnote">7</a>]</sup></p></li>
+          <sup>[<a name="id567466" href="#ftn.id567466" class="footnote">7</a>]</sup></p></li>
 </ul></div>
 <p>
     </p>
-<div class="sect2" title="C Closures">
+<div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id337933"></a>C Closures</h3></div></div></div>
+<a name="id567477"></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 <span class="type"><a class="link" href="gobject-Closures.html#GCClosure" title="GCClosure">GCClosure</a></span>s
+        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
         which have a pretty minimal API or the even simpler <code class="function"><a class="link" href="gobject-Signals.html#g-signal-connect" title="g_signal_connect()">g_signal_connect</a></code>
         functions (which will be presented a bit later :).
 </p>
@@ -132,9 +132,9 @@ GClosure *g_signal_type_cclosure_new (GType          itype,
         function if the user has supplied one.
       </p>
 </div>
-<div class="sect2" title="Non-C closures (for the fearless)">
+<div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id362303"></a>Non-C closures (for the fearless)</h3></div></div></div>
+<a name="id576670"></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 width="100" align="left">
-<div class="footnote"><p><sup>[<a id="ftn.id342247" href="#id342247" class="para">6</a>] </sup>
+<div class="footnote"><p><sup>[<a id="ftn.id545371" href="#id545371" class="para">6</a>] </sup>
         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 class="footnote"><p><sup>[<a id="ftn.id337923" href="#id337923" class="para">7</a>] </sup>
+<div class="footnote"><p><sup>[<a id="ftn.id567466" href="#id567466" class="para">7</a>] </sup>
             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>
@@ -209,6 +209,6 @@ g_cclosure_marshal_VOID__INT (GClosure     *closure,
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>

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

@@ -8,7 +8,7 @@
 <link rel="up" href="rn02.html" title="Tools Reference">
 <link rel="prev" href="glib-mkenums.html" title="glib-mkenums">
 <link rel="next" href="gobject-query.html" title="gobject-query">
-<meta name="generator" content="GTK-Doc V1.15 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.16.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -19,7 +19,7 @@
 <th width="100%" align="center">GObject Reference Manual</th>
 <td><a accesskey="n" href="gobject-query.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
 </tr></table>
-<div lang="en" class="refentry" title="glib-genmarshal">
+<div lang="en" class="refentry">
 <a name="glib-genmarshal"></a><div class="titlepage"></div>
 <div class="refnamediv"><table width="100%"><tr>
 <td valign="top">
@@ -28,12 +28,12 @@
 </td>
 <td valign="top" align="right"></td>
 </tr></table></div>
-<div class="refsynopsisdiv" title="Synopsis">
+<div class="refsynopsisdiv">
 <h2>Synopsis</h2>
 <div class="cmdsynopsis"><p><code class="command">glib-genmarshal</code>  [options...] [files...]</p></div>
 </div>
-<div class="refsect1" title="Description">
-<a name="id357609"></a><h2>Description</h2>
+<div class="refsect1">
+<a name="id573733"></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,
@@ -44,14 +44,14 @@ code function of the closure with all the parameters on the stack and to
 collect its return value.
 </p>
 </div>
-<div class="refsect1" title="Invocation">
-<a name="id359827"></a><h2>Invocation</h2>
+<div class="refsect1">
+<a name="id588300"></a><h2>Invocation</h2>
 <p><span class="command"><strong>glib-genmarshal</strong></span> takes a list of marshallers to generate as
 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" title="Options">
-<a name="id397891"></a><h3>Options</h3>
+<div class="refsect2">
+<a name="id555278"></a><h3>Options</h3>
 <div class="variablelist"><table border="0">
 <col align="left" valign="top">
 <tbody>
@@ -108,8 +108,8 @@ Print version and exit.
 </table></div>
 </div>
 <hr>
-<div class="refsect2" title="Marshaller list format">
-<a name="id371193"></a><h3>Marshaller list format</h3>
+<div class="refsect2">
+<a name="id556752"></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
@@ -136,8 +136,8 @@ which are always pointers.
 </p>
 </div>
 <hr>
-<div class="refsect2" title="Parameter types">
-<a name="id346608"></a><h3>Parameter types</h3>
+<div class="refsect2">
+<a name="id545948"></a><h3>Parameter types</h3>
 <p>
 Currently, the following types are supported:
 </p>
@@ -284,8 +284,8 @@ deprecated alias for <em class="replaceable"><code>BOOLEAN</code></em>
 </p>
 </div>
 </div>
-<div class="refsect1" title="Example">
-<a name="id369348"></a><h2>Example</h2>
+<div class="refsect1">
+<a name="id555098"></a><h2>Example</h2>
 <p>
 To generate marshallers for the following callback functions:
 </p>
@@ -332,20 +332,20 @@ cc_baz = g_cclosure_new (NULL, baz, NULL);
 g_closure_set_marshal (cc_baz, g_cclosure_marshal_FLOAT__BOOLEAN_UCHAR);
 </pre>
 </div>
-<div class="refsect1" title="See also">
-<a name="id342940"></a><h2>See also</h2>
+<div class="refsect1">
+<a name="id580932"></a><h2>See also</h2>
 <p>
 <span class="command"><strong>glib-mkenums</strong></span>(1)
 </p>
 </div>
-<div class="refsect1" title="Bugs">
-<a name="id381626"></a><h2>Bugs</h2>
+<div class="refsect1">
+<a name="id553660"></a><h2>Bugs</h2>
 <p>
 None known yet.
 </p>
 </div>
-<div class="refsect1" title="Author">
-<a name="id398658"></a><h2>Author</h2>
+<div class="refsect1">
+<a name="id559597"></a><h2>Author</h2>
 <p><span class="command"><strong>glib-genmarshal</strong></span> has been written by Tim Janik
 <code class="email">&lt;<a class="email" href="mailto:timj@gtk.org">timj@gtk.org</a>&gt;</code>.
 </p>
@@ -356,6 +356,6 @@ This manual page was provided by Tim Janik <code class="email">&lt;<a class="ema
 </div>
 <div class="footer">
 <hr>
-          Generated by GTK-Doc V1.15</div>
+          Generated by GTK-Doc V1.16.1</div>
 </body>
 </html>