RubyGems - gio2 - Versions diffs - 0.90.3-x86-mingw32 - Mend

gio2 0.90.3-x86-mingw32

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (856) hide show

data/vendor/local/share/gtk-doc/html/gobject/gtype-non-instantiable.html ADDED

@@ -0,0 +1,76 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Non-instantiable non-classed fundamental types</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GObject Reference Manual">
+<link rel="up" href="chapter-gtype.html" title="The GLib Dynamic Type System">
+<link rel="prev" href="gtype-conventions.html" title="Conventions">
+<link rel="next" href="gtype-instantiable-classed.html" title="Instantiable classed types: objects">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="gtype-conventions.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="chapter-gtype.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GObject Reference Manual</th>
+<td><a accesskey="n" href="gtype-instantiable-classed.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="sect1">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="gtype-non-instantiable"></a>Non-instantiable non-classed fundamental types</h2></div></div></div>
+<p>
+          A lot of types are not instantiable by the type system and do not have
+          a class. Most of these types are fundamental trivial types such as <span class="emphasis"><em>gchar</em></span>,
+          registered in <code class="function">g_value_types_init</code> (in <code class="filename">gvaluetypes.c</code>).
+        </p>
+<p>
+          To register such a type in the type system, you just need to fill the
+          <span class="type"><a class="link" href="gobject-Type-Information.html#GTypeInfo" title="GTypeInfo">GTypeInfo</a></span> structure with zeros since these types are also most of the time
+          fundamental:
+          </p>
+<pre class="programlisting">
+  GTypeInfo info = {
+    0,                                /* class_size */
+    NULL,                        /* base_init */
+    NULL,                        /* base_destroy */
+    NULL,                        /* class_init */
+    NULL,                        /* class_destroy */
+    NULL,                        /* class_data */
+    0,                                /* instance_size */
+    0,                                /* n_preallocs */
+    NULL,                        /* instance_init */
+    NULL,                        /* value_table */
+  };
+  static const GTypeValueTable value_table = {
+    value_init_long0,                /* value_init */
+    NULL,                        /* value_free */
+    value_copy_long0,                /* value_copy */
+    NULL,                        /* value_peek_pointer */
+    "i",                        /* collect_format */
+    value_collect_int,        /* collect_value */
+    "p",                        /* lcopy_format */
+    value_lcopy_char,                /* lcopy_value */
+  };
+  info.value_table = &amp;value_table;
+  type = g_type_register_fundamental (G_TYPE_CHAR, "gchar", &amp;info, &amp;finfo, 0);
+          </pre>
+<p>
+        </p>
+<p>
+          Having non-instantiable types might seem a bit useless: what good is a type
+          if you cannot instantiate an instance of that type ? Most of these types
+          are used in conjunction with <span class="type"><a class="link" href="gobject-Generic-values.html#GValue" title="GValue">GValue</a></span>s: a GValue is initialized
+          with an integer or a string and it is passed around by using the registered
+          type's value_table. <span class="type"><a class="link" href="gobject-Generic-values.html#GValue" title="GValue">GValue</a></span>s (and by extension these trivial fundamental
+          types) are most useful when used in conjunction with object properties and signals.
+        </p>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/gobject/home.png ADDED

Binary file

data/vendor/local/share/gtk-doc/html/gobject/howto-gobject-chainup.html ADDED

@@ -0,0 +1,100 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Chaining up</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GObject Reference Manual">
+<link rel="up" href="howto-gobject.html" title="How to define and implement a new GObject">
+<link rel="prev" href="howto-gobject-methods.html" title="Object methods">
+<link rel="next" href="howto-interface.html" title="How to define and implement interfaces">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="howto-gobject-methods.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="howto-gobject.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GObject Reference Manual</th>
+<td><a accesskey="n" href="howto-interface.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="sect1">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="howto-gobject-chainup"></a>Chaining up</h2></div></div></div>
+<p>Chaining up is often loosely defined by the following set of
+    conditions:
+      </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>Parent class A defines a public virtual method named <code class="function">foo</code> and
+        provides a default implementation.</p></li>
+<li class="listitem"><p>Child class B re-implements method <code class="function">foo</code>.</p></li>
+<li class="listitem"><p>In the method B::foo, the child class B calls its parent class method A::foo.</p></li>
+</ul></div>
+<p>
+      There are many uses to this idiom:
+      </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>You need to change the behaviour of a class without modifying its code. You create
+          a subclass to inherit its implementation, re-implement a public virtual method to modify the behaviour
+          slightly and chain up to ensure that the previous behaviour is not really modified, just extended.
+          </p></li>
+<li class="listitem"><p>You are lazy, you have access to the source code of the parent class but you don't want
+          to modify it to add method calls to new specialized method calls: it is faster to hack the child class
+          to chain up than to modify the parent to call down.</p></li>
+<li class="listitem"><p>You need to implement the Chain Of Responsibility pattern: each object of the inheritance
+          tree chains up to its parent (typically, at the beginning or the end of the method) to ensure that
+          they each handler is run in turn.</p></li>
+</ul></div>
+<p>
+      I am personally not really convinced any of the last two uses are really a good idea but since this
+      programming idiom is often used, this section attempts to explain how to implement it.
+    </p>
+<p>
+      To explicitly chain up to the implementation of the virtual method in the parent class,
+      you first need a handle to the original parent class structure. This pointer can then be used to
+      access the original class function pointer and invoke it directly.
+      <sup>[<a name="id458758" href="#ftn.id458758" class="footnote">11</a>]</sup>
+    </p>
+<p>The function <code class="function"><a class="link" href="gobject-Type-Information.html#g-type-class-peek-parent" title="g_type_class_peek_parent ()">g_type_class_peek_parent</a></code> is used to access the original parent
+    class structure. Its input is a pointer to the class of the derived object and it returns a pointer
+    to the original parent class structure. The code below shows how you could use it:
+</p>
+<pre class="programlisting">
+static void
+b_method_to_call (B *obj, int a)
+{
+  BClass *klass;
+  AClass *parent_class;
+  klass = B_GET_CLASS (obj);
+  parent_class = g_type_class_peek_parent (klass);
+  /* do stuff before chain up */
+  parent_class-&gt;method_to_call (obj, a);
+  /* do stuff after chain up */
+}
+</pre>
+<p>
+  </p>
+<div class="footnotes">
+<br><hr width="100" align="left">
+<div class="footnote"><p><sup>[<a name="ftn.id458758" href="#id458758" class="para">11</a>] </sup>
+          The <span class="emphasis"><em>original</em></span> adjective used in this sentence is not innocuous. To fully
+          understand its meaning, you need to recall how class structures are initialized: for each object type,
+          the class structure associated to this object is created by first copying the class structure of its
+          parent type (a simple <code class="function">memcpy</code>) and then by invoking the class_init callback on
+          the resulting class structure. Since the class_init callback is responsible for overwriting the class structure
+          with the user re-implementations of the class methods, we cannot merely use the modified copy of the parent class
+          structure stored in our derived instance. We want to get a copy of the class structure of an instance of the parent
+          class.
+        </p></div>
+</div>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/gobject/howto-gobject-code.html ADDED

@@ -0,0 +1,86 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Boilerplate code</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GObject Reference Manual">
+<link rel="up" href="howto-gobject.html" title="How to define and implement a new GObject">
+<link rel="prev" href="howto-gobject.html" title="How to define and implement a new GObject">
+<link rel="next" href="howto-gobject-construction.html" title="Object Construction">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="howto-gobject.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="howto-gobject.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GObject Reference Manual</th>
+<td><a accesskey="n" href="howto-gobject-construction.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="sect1">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="howto-gobject-code"></a>Boilerplate code</h2></div></div></div>
+<p>
+      In your code, the first step is to #include the needed headers: depending
+      on your header include strategy, this can be as simple as
+      <code class="literal">#include "maman-bar.h"</code> or as complicated as tens
+      of #include lines ending with <code class="literal">#include "maman-bar.h"</code>:
+</p>
+<pre class="programlisting">
+/*
+ * Copyright information
+ */
+#include "maman-bar.h"
+/* If you use Pimpls, include the private structure
+ * definition here. Some people create a maman-bar-private.h header
+ * which is included by the maman-bar.c file and which contains the
+ * definition for this private structure.
+ */
+struct _MamanBarPrivate {
+  int member_1;
+  /* stuff */
+};
+/*
+ * forward definitions
+ */
+</pre>
+<p>
+    </p>
+<p>
+      Call the <code class="function">G_DEFINE_TYPE</code> macro using the name
+      of the type, the prefix of the functions and the parent GType to
+      reduce the amount of boilerplate needed. This macro will:
+      </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">implement the <code class="function">maman_bar_get_type</code>
+        function</li>
+<li class="listitem">define a parent class pointer accessible from
+        the whole .c file</li>
+</ul></div>
+<p>
+</p>
+<pre class="programlisting">
+G_DEFINE_TYPE (MamanBar, maman_bar, G_TYPE_OBJECT);
+</pre>
+<p>
+    </p>
+<p>
+      It is also possible to use the
+      <code class="function">G_DEFINE_TYPE_WITH_CODE</code> macro to control the
+      get_type function implementation - for instance, to add a call to
+      <code class="function">G_IMPLEMENT_INTERFACE</code> macro which will
+      call the <code class="function">g_type_implement_interface</code> function.
+    </p>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/gobject/howto-gobject-construction.html ADDED

@@ -0,0 +1,113 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Object Construction</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GObject Reference Manual">
+<link rel="up" href="howto-gobject.html" title="How to define and implement a new GObject">
+<link rel="prev" href="howto-gobject-code.html" title="Boilerplate code">
+<link rel="next" href="howto-gobject-destruction.html" title="Object Destruction">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="howto-gobject-code.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="howto-gobject.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GObject Reference Manual</th>
+<td><a accesskey="n" href="howto-gobject-destruction.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="sect1">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="howto-gobject-construction"></a>Object Construction</h2></div></div></div>
+<p>
+      People often get confused when trying to construct their GObjects because of the
+      sheer number of different ways to hook into the objects's construction process: it is
+      difficult to figure which is the <span class="emphasis"><em>correct</em></span>, recommended way.
+    </p>
+<p>
+      <a class="xref" href="chapter-gobject.html#gobject-construction-table" title="Table 4. g_object_new">Table 4, “g_object_new”</a> shows what user-provided functions
+      are invoked during object instantiation and in which order they are invoked.
+      A user looking for the equivalent of the simple C++ constructor function should use
+      the instance_init method. It will be invoked after all the parent's instance_init
+      functions have been invoked. It cannot take arbitrary construction parameters
+      (as in C++) but if your object needs arbitrary parameters to complete initialization,
+      you can use construction properties.
+    </p>
+<p>
+      Construction properties will be set only after all instance_init functions have run.
+      No object reference will be returned to the client of <code class="function"><a class="link" href="gobject-The-Base-Object-Type.html#g-object-new" title="g_object_new ()">g_object_new</a></code>
+      until all the construction properties have been set.
+    </p>
+<p>
+      As such, I would recommend writing the following code first:
+</p>
+<pre class="programlisting">
+static void
+maman_bar_init (MamanBar *self)
+{
+  self-&gt;priv = MAMAN_BAR_GET_PRIVATE (self);
+  /* initialize all public and private members to reasonable default values. */
+  /* If you need specific construction properties to complete initialization,
+   * delay initialization completion until the property is set.
+   */
+}
+</pre>
+<p>
+    </p>
+<p>
+      Now, if you need special construction properties, install the properties in the class_init function,
+      override the set and get methods and implement the get and set methods as described in
+      <a class="xref" href="gobject-properties.html" title="Object properties">the section called “Object properties”</a>. Make sure that these properties use a construct only
+      <span class="type"><a class="link" href="gobject-GParamSpec.html#GParamSpec" title="GParamSpec">GParamSpec</a></span> by setting the param spec's flag field to G_PARAM_CONSTRUCT_ONLY: this helps
+      GType ensure that these properties are not set again later by malicious user code.
+</p>
+<pre class="programlisting">
+static void
+bar_class_init (MamanBarClass *klass)
+{
+  GObjectClass *gobject_class = G_OBJECT_CLASS (klass);
+  GParamSpec *maman_param_spec;
+  gobject_class-&gt;set_property = bar_set_property;
+  gobject_class-&gt;get_property = bar_get_property;
+  maman_param_spec = g_param_spec_string ("maman",
+                                          "Maman construct prop",
+                                          "Set maman's name",
+                                          "no-name-set" /* default value */,
+                                          G_PARAM_CONSTRUCT_ONLY | G_PARAM_READWRITE);
+  g_object_class_install_property (gobject_class,
+                                   PROP_MAMAN,
+                                   maman_param_spec);
+}
+</pre>
+<p>
+      If you need this, make sure you can build and run code similar to the code shown above. Make sure
+      your construct properties can set correctly during construction, make sure you cannot set them
+      afterwards and make sure that if your users do not call <code class="function"><a class="link" href="gobject-The-Base-Object-Type.html#g-object-new" title="g_object_new ()">g_object_new</a></code>
+      with the required construction properties, these will be initialized with the default values.
+    </p>
+<p>
+      I consider good taste to halt program execution if a construction property is set its
+      default value. This allows you to catch client code which does not give a reasonable
+      value to the construction properties. Of course, you are free to disagree but you
+      should have a good reason to do so.
+    </p>
+<p>
+      Some people sometimes need to construct their object but only after
+      the construction properties have been set. This is possible through
+      the use of the constructor class method as described in
+      <a class="xref" href="chapter-gobject.html#gobject-instantiation" title="Object instantiation">the section called “Object instantiation”</a> or, more simply, using
+      the constructed class method available since GLib 2.12.
+    </p>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/gobject/howto-gobject-destruction.html ADDED

@@ -0,0 +1,122 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Object Destruction</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GObject Reference Manual">
+<link rel="up" href="howto-gobject.html" title="How to define and implement a new GObject">
+<link rel="prev" href="howto-gobject-construction.html" title="Object Construction">
+<link rel="next" href="howto-gobject-methods.html" title="Object methods">
+<meta name="generator" content="GTK-Doc V1.15.1 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="howto-gobject-construction.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="howto-gobject.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GObject Reference Manual</th>
+<td><a accesskey="n" href="howto-gobject-methods.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="sect1">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="howto-gobject-destruction"></a>Object Destruction</h2></div></div></div>
+<p>
+      Again, it is often difficult to figure out which mechanism to use to
+      hook into the object's destruction process: when the last
+      <code class="function"><a class="link" href="gobject-The-Base-Object-Type.html#g-object-unref" title="g_object_unref ()">g_object_unref</a></code>
+      function call is made, a lot of things happen as described in
+      <a class="xref" href="gobject-memory.html#gobject-destruction-table" title="Table 5. g_object_unref">Table 5, “g_object_unref”</a>.
+    </p>
+<p>
+      The destruction process of your object might be split in two different
+      phases: dispose and the finalize.
+</p>
+<pre class="programlisting">
+#define MAMAN_BAR_GET_PRIVATE(obj) (G_TYPE_INSTANCE_GET_PRIVATE ((obj), MAMAN_TYPE_BAR, MamanBarPrivate))
+struct _MamanBarPrivate
+{
+  GObject *an_object;
+  gchar *a_string;
+};
+G_DEFINE_TYPE (MamanBar, maman_bar, G_TYPE_OBJECT);
+static void
+maman_bar_dispose (GObject *gobject)
+{
+  MamanBar *self = MAMAN_BAR (gobject);
+  /*
+   * In dispose, you are supposed to free all types referenced from this
+   * object which might themselves hold a reference to self. Generally,
+   * the most simple solution is to unref all members on which you own a
+   * reference.
+   */
+  /* dispose might be called multiple times, so we must guard against
+   * calling g_object_unref() on an invalid GObject.
+   */
+  if (self-&gt;priv-&gt;an_object)
+    {
+      g_object_unref (self-&gt;priv-&gt;an_object);
+      self-&gt;priv-&gt;an_object = NULL;
+    }
+  /* Chain up to the parent class */
+  G_OBJECT_CLASS (maman_bar_parent_class)-&gt;dispose (gobject);
+}
+static void
+maman_bar_finalize (GObject *gobject)
+{
+  MamanBar *self = MAMAN_BAR (gobject);
+  g_free (self-&gt;priv-&gt;a_string);
+  /* Chain up to the parent class */
+  G_OBJECT_CLASS (maman_bar_parent_class)-&gt;finalize (gobject);
+}
+static void
+maman_bar_class_init (MamanBarClass *klass)
+{
+  GObjectClass *gobject_class = G_OBJECT_CLASS (klass);
+  gobject_class-&gt;dispose = maman_bar_dispose;
+  gobject_class-&gt;finalize = maman_bar_finalize;
+  g_type_class_add_private (klass, sizeof (MamanBarPrivate));
+}
+static void
+maman_bar_init (MamanBar *self);
+{
+  self-&gt;priv = MAMAN_BAR_GET_PRIVATE (self);
+  self-&gt;priv-&gt;an_object = g_object_new (MAMAN_TYPE_BAZ, NULL);
+  self-&gt;priv-&gt;a_string = g_strdup ("Maman");
+}
+</pre>
+<p>
+    </p>
+<p>
+      Add similar code to your GObject, make sure the code still builds
+      and runs: dispose and finalize must be called during the last unref.
+    </p>
+<p>
+      It is possible that object methods might be invoked after dispose is
+      run and before finalize runs. GObject does not consider this to be a
+      program error: you must gracefully detect this and neither crash nor
+      warn the user.
+    </p>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.15.1</div>
+</body>
+</html>