moved includes back to the top of the files (before gtk-doc SECTION

2008-06-22  Michael Natterer  <mitch@imendio.com>

	* *.c: moved includes back to the top of the files (before gtk-doc
	SECTION comments). Add "config.h" in all files and move system
	included before glib includes. Remove trailing whitespace from
	SECTION comments and did some reformatting where lines were overly
	long, no documentation content was changed.


svn path=/trunk/; revision=7089

1 files changed, 28 insertions, 23 deletions

diff --git a/gobject/gtypeplugin.c b/gobject/gtypeplugin.c
index 8aaa7e4d6..12698b01c 100644
--- a/gobject/gtypeplugin.c
+++ b/gobject/gtypeplugin.c
@@ -16,16 +16,23 @@
  * Free Software Foundation, Inc., 59 Temple Place, Suite 330,
  * Boston, MA 02111-1307, USA.
  */
+
+#include "config.h"
+
+#include "gtypeplugin.h"
+#include "gobjectalias.h"
+
+
 /**
  * SECTION:gtypeplugin
  * @Short_description: An interface for dynamically loadable types
  * @See_also:#GTypeModule and g_type_register_dynamic().
  * @Titile: GTypePlugin
- * 
- * The GObject type system supports dynamic loading of types. The #GTypePlugin 
- * interface is used to handle the lifecycle of dynamically loaded types. 
- * It goes as follows:
- * 
+ *
+ * The GObject type system supports dynamic loading of types. The
+ * #GTypePlugin interface is used to handle the lifecycle of
+ * dynamically loaded types.  It goes as follows:
+ *
  * <orderedlist>
  * <listitem><para>
  *   The type is initially introduced (usually upon loading the module
@@ -42,13 +49,13 @@
  * </para></listitem>
  * <listitem><para>
  *    The type's implementation is referenced, e.g. through
- *    g_type_class_ref() or through g_type_create_instance() (this is 
- *    being called by g_object_new()) or through one of the above done on 
+ *    g_type_class_ref() or through g_type_create_instance() (this is
+ *    being called by g_object_new()) or through one of the above done on
  *    a type derived from <literal>new_type_id</literal>.
  * </para></listitem>
  * <listitem><para>
  *    This causes the type system to load the type's implementation by calling
- *    g_type_plugin_use() and g_type_plugin_complete_type_info() on 
+ *    g_type_plugin_use() and g_type_plugin_complete_type_info() on
  *    <literal>new_type_plugin</literal>.
  * </para></listitem>
  * <listitem><para>
@@ -65,22 +72,20 @@
  *    Things may repeat from the second step.
  * </para></listitem>
  * </orderedlist>
- * 
- * So basically, you need to implement a #GTypePlugin type that carries a
- * use_count, once use_count goes from zero to one, you need to load the 
- * implementation to successfully handle the upcoming 
- * g_type_plugin_complete_type_info() call. Later, maybe after succeeding 
- * use/unuse calls, once use_count drops to zero, you can unload the 
- * implementation again. The type system makes sure to call g_type_plugin_use() 
- * and g_type_plugin_complete_type_info() again when the type is needed again.
- * 
- * #GTypeModule is an implementation of #GTypePlugin that already implements 
- * most of this except for the actual module loading and unloading. It even 
- * handles multiple registered types per module.
+ *
+ * So basically, you need to implement a #GTypePlugin type that
+ * carries a use_count, once use_count goes from zero to one, you need
+ * to load the implementation to successfully handle the upcoming
+ * g_type_plugin_complete_type_info() call. Later, maybe after
+ * succeeding use/unuse calls, once use_count drops to zero, you can
+ * unload the implementation again. The type system makes sure to call
+ * g_type_plugin_use() and g_type_plugin_complete_type_info() again
+ * when the type is needed again.
+ *
+ * #GTypeModule is an implementation of #GTypePlugin that already
+ * implements most of this except for the actual module loading and
+ * unloading. It even handles multiple registered types per module.
  */
-#include	"gtypeplugin.h"
-#include	"gobjectalias.h"
-
 
 
 /* --- functions --- */