Author: paul
Date: 2007-10-27 19:52:33 +0200 (Sat, 27 Oct 2007)
New Revision: 8357
Log:
r21572@kite-hub: paul | 2007-10-27 11:49:38 -0500
Add markup.
Modified:
trunk/refman-4.1/apis-c.xml
trunk/refman-5.0/apis-c.xml
trunk/refman-5.1/apis-c.xml
trunk/refman-5.2/apis-c.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:31743
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:26243
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:21534
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:31743
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:26243
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:21572
Modified: trunk/refman-4.1/apis-c.xml
===================================================================
--- trunk/refman-4.1/apis-c.xml 2007-10-27 15:59:38 UTC (rev 8356)
+++ trunk/refman-4.1/apis-c.xml 2007-10-27 17:52:33 UTC (rev 8357)
Changed blocks: 3, Lines Added: 18, Lines Deleted: 16; 3266 bytes
@@ -12787,28 +12787,30 @@
</para>
<para>
- <literal>my_init()</literal> initializes some global variables
- that MySQL needs. If you are using a thread-safe client library,
- it also calls <literal>mysql_thread_init()</literal> for this
- thread.
+ <function role="capi">my_init()</function> initializes some
+ global variables that MySQL needs. If you are using a
+ thread-safe client library, it also calls
+ <literal>mysql_thread_init()</literal> for this thread.
</para>
<para>
- It is necessary for <literal>my_init()</literal> to be called
- early in the initialization phase of a program's use of the
- MySQL library. However, <literal>my_init()</literal> is
- automatically called by <literal>mysql_init()</literal>,
+ It is necessary for <function role="capi">my_init()</function>
+ to be called early in the initialization phase of a program's
+ use of the MySQL library. However,
+ <function role="capi">my_init()</function> is automatically
+ called by <literal>mysql_init()</literal>,
<literal>mysql_library_init()</literal>,
<literal>mysql_server_init()</literal>, and
<literal>mysql_connect()</literal>. If you ensure that your
program invokes one of those functions before any other MySQL
- calls, there is no need to invoke <literal>my_init()</literal>
- explicitly.
+ calls, there is no need to invoke
+ <function role="capi">my_init()</function> explicitly.
</para>
<para>
- To access <literal>my_init()</literal>, your program must
- include the <filename>my_sys.h</filename> header file:
+ To access <function role="capi">my_init()</function>, your
+ program must include the <filename>my_sys.h</filename> header
+ file:
</para>
<programlisting>
@@ -12884,8 +12886,8 @@
initialize thread-specific variables. However, you may not
necessarily need to invoke it explicitly:
<literal>mysql_thread_init()</literal> is automatically called
- by <literal>my_init()</literal>, which itself is automatically
- called by <literal>mysql_init()</literal>,
+ by <function role="capi">my_init()</function>, which itself is
+ automatically called by <literal>mysql_init()</literal>,
<literal>mysql_library_init()</literal>,
<literal>mysql_server_init()</literal>, and
<literal>mysql_connect()</literal>. If you invoke any of those
@@ -13637,8 +13639,8 @@
interrupts, you can make great use of the routines in the
<filename>thr_alarm.c</filename> file. If you are using routines
from the <literal>mysys</literal> library, the only thing you must
- remember is to call <literal>my_init()</literal> first! See
- <xref linkend="c-thread-functions"/>.
+ remember is to call <function role="capi">my_init()</function>
+ first! See <xref linkend="c-thread-functions"/>.
</para>
<para>
Modified: trunk/refman-5.0/apis-c.xml
===================================================================
--- trunk/refman-5.0/apis-c.xml 2007-10-27 15:59:38 UTC (rev 8356)
+++ trunk/refman-5.0/apis-c.xml 2007-10-27 17:52:33 UTC (rev 8357)
Changed blocks: 3, Lines Added: 18, Lines Deleted: 16; 3266 bytes
@@ -12920,28 +12920,30 @@
</para>
<para>
- <literal>my_init()</literal> initializes some global variables
- that MySQL needs. If you are using a thread-safe client library,
- it also calls <literal>mysql_thread_init()</literal> for this
- thread.
+ <function role="capi">my_init()</function> initializes some
+ global variables that MySQL needs. If you are using a
+ thread-safe client library, it also calls
+ <literal>mysql_thread_init()</literal> for this thread.
</para>
<para>
- It is necessary for <literal>my_init()</literal> to be called
- early in the initialization phase of a program's use of the
- MySQL library. However, <literal>my_init()</literal> is
- automatically called by <literal>mysql_init()</literal>,
+ It is necessary for <function role="capi">my_init()</function>
+ to be called early in the initialization phase of a program's
+ use of the MySQL library. However,
+ <function role="capi">my_init()</function> is automatically
+ called by <literal>mysql_init()</literal>,
<literal>mysql_library_init()</literal>,
<literal>mysql_server_init()</literal>, and
<literal>mysql_connect()</literal>. If you ensure that your
program invokes one of those functions before any other MySQL
- calls, there is no need to invoke <literal>my_init()</literal>
- explicitly.
+ calls, there is no need to invoke
+ <function role="capi">my_init()</function> explicitly.
</para>
<para>
- To access <literal>my_init()</literal>, your program must
- include the <filename>my_sys.h</filename> header file:
+ To access <function role="capi">my_init()</function>, your
+ program must include the <filename>my_sys.h</filename> header
+ file:
</para>
<programlisting>
@@ -13017,8 +13019,8 @@
initialize thread-specific variables. However, you may not
necessarily need to invoke it explicitly:
<literal>mysql_thread_init()</literal> is automatically called
- by <literal>my_init()</literal>, which itself is automatically
- called by <literal>mysql_init()</literal>,
+ by <function role="capi">my_init()</function>, which itself is
+ automatically called by <literal>mysql_init()</literal>,
<literal>mysql_library_init()</literal>,
<literal>mysql_server_init()</literal>, and
<literal>mysql_connect()</literal>. If you invoke any of those
@@ -13786,8 +13788,8 @@
interrupts, you can make great use of the routines in the
<filename>thr_alarm.c</filename> file. If you are using routines
from the <literal>mysys</literal> library, the only thing you must
- remember is to call <literal>my_init()</literal> first! See
- <xref linkend="c-thread-functions"/>.
+ remember is to call <function role="capi">my_init()</function>
+ first! See <xref linkend="c-thread-functions"/>.
</para>
<para>
Modified: trunk/refman-5.1/apis-c.xml
===================================================================
--- trunk/refman-5.1/apis-c.xml 2007-10-27 15:59:38 UTC (rev 8356)
+++ trunk/refman-5.1/apis-c.xml 2007-10-27 17:52:33 UTC (rev 8357)
Changed blocks: 3, Lines Added: 18, Lines Deleted: 16; 3266 bytes
@@ -13003,28 +13003,30 @@
</para>
<para>
- <literal>my_init()</literal> initializes some global variables
- that MySQL needs. If you are using a thread-safe client library,
- it also calls <literal>mysql_thread_init()</literal> for this
- thread.
+ <function role="capi">my_init()</function> initializes some
+ global variables that MySQL needs. If you are using a
+ thread-safe client library, it also calls
+ <literal>mysql_thread_init()</literal> for this thread.
</para>
<para>
- It is necessary for <literal>my_init()</literal> to be called
- early in the initialization phase of a program's use of the
- MySQL library. However, <literal>my_init()</literal> is
- automatically called by <literal>mysql_init()</literal>,
+ It is necessary for <function role="capi">my_init()</function>
+ to be called early in the initialization phase of a program's
+ use of the MySQL library. However,
+ <function role="capi">my_init()</function> is automatically
+ called by <literal>mysql_init()</literal>,
<literal>mysql_library_init()</literal>,
<literal>mysql_server_init()</literal>, and
<literal>mysql_connect()</literal>. If you ensure that your
program invokes one of those functions before any other MySQL
- calls, there is no need to invoke <literal>my_init()</literal>
- explicitly.
+ calls, there is no need to invoke
+ <function role="capi">my_init()</function> explicitly.
</para>
<para>
- To access <literal>my_init()</literal>, your program must
- include the <filename>my_sys.h</filename> header file:
+ To access <function role="capi">my_init()</function>, your
+ program must include the <filename>my_sys.h</filename> header
+ file:
</para>
<programlisting>
@@ -13100,8 +13102,8 @@
initialize thread-specific variables. However, you may not
necessarily need to invoke it explicitly:
<literal>mysql_thread_init()</literal> is automatically called
- by <literal>my_init()</literal>, which itself is automatically
- called by <literal>mysql_init()</literal>,
+ by <function role="capi">my_init()</function>, which itself is
+ automatically called by <literal>mysql_init()</literal>,
<literal>mysql_library_init()</literal>,
<literal>mysql_server_init()</literal>, and
<literal>mysql_connect()</literal>. If you invoke any of those
@@ -13844,8 +13846,8 @@
interrupts, you can make great use of the routines in the
<filename>thr_alarm.c</filename> file. If you are using routines
from the <literal>mysys</literal> library, the only thing you must
- remember is to call <literal>my_init()</literal> first! See
- <xref linkend="c-thread-functions"/>.
+ remember is to call <function role="capi">my_init()</function>
+ first! See <xref linkend="c-thread-functions"/>.
</para>
<para>
Modified: trunk/refman-5.2/apis-c.xml
===================================================================
--- trunk/refman-5.2/apis-c.xml 2007-10-27 15:59:38 UTC (rev 8356)
+++ trunk/refman-5.2/apis-c.xml 2007-10-27 17:52:33 UTC (rev 8357)
Changed blocks: 3, Lines Added: 18, Lines Deleted: 16; 3266 bytes
@@ -12939,28 +12939,30 @@
</para>
<para>
- <literal>my_init()</literal> initializes some global variables
- that MySQL needs. If you are using a thread-safe client library,
- it also calls <literal>mysql_thread_init()</literal> for this
- thread.
+ <function role="capi">my_init()</function> initializes some
+ global variables that MySQL needs. If you are using a
+ thread-safe client library, it also calls
+ <literal>mysql_thread_init()</literal> for this thread.
</para>
<para>
- It is necessary for <literal>my_init()</literal> to be called
- early in the initialization phase of a program's use of the
- MySQL library. However, <literal>my_init()</literal> is
- automatically called by <literal>mysql_init()</literal>,
+ It is necessary for <function role="capi">my_init()</function>
+ to be called early in the initialization phase of a program's
+ use of the MySQL library. However,
+ <function role="capi">my_init()</function> is automatically
+ called by <literal>mysql_init()</literal>,
<literal>mysql_library_init()</literal>,
<literal>mysql_server_init()</literal>, and
<literal>mysql_connect()</literal>. If you ensure that your
program invokes one of those functions before any other MySQL
- calls, there is no need to invoke <literal>my_init()</literal>
- explicitly.
+ calls, there is no need to invoke
+ <function role="capi">my_init()</function> explicitly.
</para>
<para>
- To access <literal>my_init()</literal>, your program must
- include the <filename>my_sys.h</filename> header file:
+ To access <function role="capi">my_init()</function>, your
+ program must include the <filename>my_sys.h</filename> header
+ file:
</para>
<programlisting>
@@ -13036,8 +13038,8 @@
initialize thread-specific variables. However, you may not
necessarily need to invoke it explicitly:
<literal>mysql_thread_init()</literal> is automatically called
- by <literal>my_init()</literal>, which itself is automatically
- called by <literal>mysql_init()</literal>,
+ by <function role="capi">my_init()</function>, which itself is
+ automatically called by <literal>mysql_init()</literal>,
<literal>mysql_library_init()</literal>,
<literal>mysql_server_init()</literal>, and
<literal>mysql_connect()</literal>. If you invoke any of those
@@ -13749,8 +13751,8 @@
interrupts, you can make great use of the routines in the
<filename>thr_alarm.c</filename> file. If you are using routines
from the <literal>mysys</literal> library, the only thing you must
- remember is to call <literal>my_init()</literal> first! See
- <xref linkend="c-thread-functions"/>.
+ remember is to call <function role="capi">my_init()</function>
+ first! See <xref linkend="c-thread-functions"/>.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8357 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.2 | paul | 27 Oct |
