[gtkmm-documentation] gmmproc Parameter Reordering: Include a warning for _WRAP_SIGNAL().

[José Alburquerque <jaalburqu src gnome org>]

commit 026751c0b33bda569edf43f46339298ed156a9b5
Author: José Alburquerque <jaalburquerque gmail com>
Date:   Sun Jun 30 17:40:49 2013 -0400

    gmmproc Parameter Reordering: Include a warning for _WRAP_SIGNAL().
    
        * docs/tutorial/C/gtkmm-tutorial-in.xml: It is necessary to warn that
        the C parameter names for C signals are always p0, p1, etc. because
        the extra defs utility generates the signals that way presently.

 docs/tutorial/C/gtkmm-tutorial-in.xml |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)
---
diff --git a/docs/tutorial/C/gtkmm-tutorial-in.xml b/docs/tutorial/C/gtkmm-tutorial-in.xml
index 53ccc9e..cb89bf5 100644
--- a/docs/tutorial/C/gtkmm-tutorial-in.xml
+++ b/docs/tutorial/C/gtkmm-tutorial-in.xml
@@ -9731,6 +9731,16 @@ _MEMBER_GET_GOBJECT(layout, layout, Pango::Layout, PangoLayout*)
         gtk_widget_set_device_events)
       </programlisting>
     </para>
+    <warning>
+      <para>
+        Please note that when reording parameters for a
+        <function>_WRAP_SIGNAL()</function> method signature, the C parameter
+        names would always be <literal>p0</literal>, <literal>p1</literal>,
+        etc. because the <filename>extra_defs</filename> utility uses those
+        parameter names no matter what the C API's parameter names may be.
+        It's how the utility is written presently.
+      </para>
+    </warning>
   </sect3>
 
   <sect3 id="gmmproc-optional-parameter-processing">