add some missing "typedef" keywords for prototyped function-pointers.

also, use "type" markup in some of the places where it's needed.

Signed-off-by: Thomas E. Dickey <dickey@invisible-island.net>

5 files changed, 15 insertions, 15 deletions

diff --git a/specs/CH01.xml b/specs/CH01.xml
index 8d77f87..e1558cd 100644
--- a/specs/CH01.xml
+++ b/specs/CH01.xml
@@ -2226,7 +2226,7 @@ The class_part_initialize procedure pointer is of type
 
 <funcsynopsis>
 <funcprototype>
-  <funcdef>void <function>(*XtWidgetClassProc)(WidgetClass)</function></funcdef>
+  <funcdef>typedef void <function>(*XtWidgetClassProc)(WidgetClass)</function></funcdef>
   <paramdef>WidgetClass<parameter> widget_class</parameter></paramdef>
 </funcprototype>
 </funcsynopsis>
diff --git a/specs/CH02.xml b/specs/CH02.xml
index 0abf557..ef2d123 100644
--- a/specs/CH02.xml
+++ b/specs/CH02.xml
@@ -3189,7 +3189,7 @@ The initialize_hook procedure pointer is of type
 
 <funcsynopsis id='XtArgsProc'>
 <funcprototype>
-  <funcdef>typedef void<function>(*XtArgsProc)</function></funcdef>
+  <funcdef>typedef void <function>(*XtArgsProc)</function></funcdef>
   <paramdef>Widget <parameter>w</parameter></paramdef>
   <paramdef>ArgList <parameter>args</parameter></paramdef>
   <paramdef>Cardinal * <parameter>num_args</parameter></paramdef>
diff --git a/specs/CH05.xml b/specs/CH05.xml
index 97974bd..bc692b1 100644
--- a/specs/CH05.xml
+++ b/specs/CH05.xml
@@ -406,7 +406,7 @@ in the shell widget instance record is of type
 
 <funcsynopsis id='XtCreatePopupChildProc'>
 <funcprototype>
-<funcdef>void <function>*XtCreatePopupChildProc</function></funcdef>
+<funcdef>typedef void <function>*XtCreatePopupChildProc</function></funcdef>
    <paramdef>Widget <parameter>w</parameter></paramdef>
 </funcprototype>
 </funcsynopsis>
diff --git a/specs/CH07.xml b/specs/CH07.xml
index 94c666a..bccd341 100644
--- a/specs/CH07.xml
+++ b/specs/CH07.xml
@@ -391,7 +391,7 @@ are of type
 
 <funcsynopsis id='XtBlockHookProc'>
 <funcprototype>
-<funcdef>void <function>*XtBlockHookProc</function></funcdef>
+<funcdef>typedef void <function>*XtBlockHookProc</function></funcdef>
    <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
 </funcprototype>
 </funcsynopsis>
@@ -532,7 +532,7 @@ type
 
 <funcsynopsis id='XtTimerCallbackProc'>
 <funcprototype>
-<funcdef>void <function>*XtTimerCallbackProc</function></funcdef>
+<funcdef>typedef void <function>*XtTimerCallbackProc</function></funcdef>
    <paramdef>XtPointer <parameter>client_data</parameter></paramdef>
    <paramdef>XtIntervalId *<parameter>timer</parameter></paramdef>
 </funcprototype>
diff --git a/specs/CH13.xml b/specs/CH13.xml
index b9d8e59..ac8ef5a 100644
--- a/specs/CH13.xml
+++ b/specs/CH13.xml
@@ -917,7 +917,7 @@ Used with a K&amp;R compiler, those parameters were ignored.
 <itemizedlist>
 <listitem>
 <para>
-The X Toolkit library used <code>const</code> in just a few cases.
+The X Toolkit library used <type>const</type> in just a few cases.
 The specification did not mention it at all.
 </para>
 <para>
@@ -978,8 +978,8 @@ and
 <listitem>
 <para>
 Several prototypes in the implementation
-use the private type <code>_XtString</code>.
-The specification and implementation also used a <code>String</code>
+use the private type <type>_XtString</type>.
+The specification and implementation also used a <type>String</type>
 type without explaining when it is appropriate.
 <programlisting>
 typedef char *String;
@@ -993,12 +993,12 @@ typedef char *String;
 </programlisting>
 That is, the developers were providing for some workaround to allow
 C++ applications to use the stricter compiler checking
-associated with <code>const</code>.
+associated with <type>const</type>.
 </para>
 </listitem>
 <listitem>
 <para>
-The <code>String</code> type is not the only type used in the
+The <type>String</type> type is not the only type used in the
 prototypes for the X Toolkit library.
 Its developers were also concerned with porting the library
 to platforms with different size-constraints.
@@ -1034,8 +1034,8 @@ typedef unsigned char	XtEnum;
 </programlisting>
 In practice, wide-prototypes are rarely used, not well supported.
 The specification did not clarify the distinction
-between <code>Bool</code> (mentioned as a resource type)
-and <code>Boolean</code> (used in all of the data structures).
+between <type>Bool</type> (mentioned as a resource type)
+and <type>Boolean</type> (used in all of the data structures).
 The implementation used both, predominantly the latter.
 </para>
 </listitem>
@@ -1047,14 +1047,14 @@ it was accommodating K&amp;R C:
 <itemizedlist>
 <listitem>
 <para>
-K&amp;R C has no <code>void</code> keyword.
+K&amp;R C has no <type>void</type> keyword.
 The specification used it for return-types,
 but not to indicate an empty parameter list.
 The specification also stated that
-<code>void*</code> would be used for the <code>XtPointer</code> type.
+<type>void*</type> would be used for the <type>XtPointer</type> type.
 </para>
 <para>
-The conversion to sgml lost the <code>void</code> return-type.
+The conversion to sgml lost the <type>void</type> return-type.
 </para>
 </listitem>
 <listitem>