/soc/2013/ankitkv/gobjectification: d8b39c2329dd: Use func() for...

[Ankit Vani]

Changeset: d8b39c2329dd8a4b93348d7efc56fde253bf3040
Author:	 Ankit Vani <a at nevitus.org>
Date:	 2014-02-03 02:52 +0530
Branch:	 gtkdoc-conversion
URL: https://hg.pidgin.im/soc/2013/ankitkv/gobjectification/rev/d8b39c2329dd

Description:

Use func() format for functions in signals tuts

diffstat:

 doc/reference/libpurple/tut_signals.xml |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (38 lines):

diff --git a/doc/reference/libpurple/tut_signals.xml b/doc/reference/libpurple/tut_signals.xml
--- a/doc/reference/libpurple/tut_signals.xml
+++ b/doc/reference/libpurple/tut_signals.xml
@@ -35,7 +35,7 @@
   callbacks may be connected to it. This is done using
   <link linkend="purple-signal-register"><function>purple_signal_register()</function></link>.
   Here is a slightly modified example from
-  <link linkend="purple-plugins-init"><function>purple_plugins_init</function></link>
+  <link linkend="purple-plugins-init"><function>purple_plugins_init()</function></link>
   in <literal>plugin.c</literal>:
 
 <programlisting>
@@ -111,7 +111,7 @@ gboolean cb(void *arg1, void *arg2, void
   <literal>PURPLE_TYPE_PLUGIN</literal> specifies that the first argument given to the callback
   will be a <literal>PurplePlugin*</literal>. You will need as many "type of argument"
   arguments to
-  <link linkend="purple-signal-register"><function>purple_signal_register</function></link>
+  <link linkend="purple-signal-register"><function>purple_signal_register()</function></link>
   as you specified in
   "Number of arguments" above.
 
@@ -180,14 +180,14 @@ purple_signal_connect(purple_plugins_get
   </para>
 
   <para>
-  As seen in <link linkend="purple-plugin-load"><function>purple_plugin_load</function></link>
+  As seen in <link linkend="purple-plugin-load"><function>purple_plugin_load()</function></link>
   in plugin.c:
 <programlisting>
 purple_signal_emit(purple_plugins_get_handle(), "plugin-load", plugin);
 </programlisting>
   This causes the signal "plugin-load" to be emitted from the plugin module
   (given by
-  <link linkend="purple-plugins-get-handle"><function>purple_plugins_get_handle</function></link>),
+  <link linkend="purple-plugins-get-handle"><function>purple_plugins_get_handle()</function></link>),
   with the newly loaded plugin as
   the argument to pass to any registered callback functions.
   </para>