diff options
Diffstat (limited to 'docs/programmer_reference/program_namespace.html')
| -rw-r--r-- | docs/programmer_reference/program_namespace.html | 105 |
1 files changed, 65 insertions, 40 deletions
diff --git a/docs/programmer_reference/program_namespace.html b/docs/programmer_reference/program_namespace.html index 46cedbe4..8363cd50 100644 --- a/docs/programmer_reference/program_namespace.html +++ b/docs/programmer_reference/program_namespace.html @@ -14,7 +14,7 @@ <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> @@ -22,9 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="program_scope.html">Prev</a> </td> - <th width="60%" align="center">Chapter 15. - Programmer Notes - </th> + <th width="60%" align="center">Chapter 15. Programmer Notes </th> <td width="20%" align="right"> <a accesskey="n" href="program_ram.html">Next</a></td> </tr> </table> @@ -42,12 +40,13 @@ <dl> <dt> <span class="sect2"> - <a href="program_namespace.html#idp2805992">C Language Name Space</a> + <a href="program_namespace.html#idp2522952">C Language Name + Space</a> </span> </dt> <dt> <span class="sect2"> - <a href="program_namespace.html#idp2778712">Filesystem Name Space</a> + <a href="program_namespace.html#idp2540280">Filesystem Name Space</a> </span> </dt> </dl> @@ -56,50 +55,75 @@ <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp2805992"></a>C Language Name Space</h3> + <h3 class="title"><a id="idp2522952"></a>C Language Name + Space</h3> </div> </div> </div> - <p>The Berkeley DB library is careful to avoid C language programmer name spaces, -but there are a few potential areas for concern, mostly in the Berkeley DB -include file db.h. The db.h include file defines a number of types and -strings. Where possible, all of these types and strings are prefixed with -"DB_" or "db_". There are a few notable exceptions.</p> - <p>The Berkeley DB library uses a macro named "__P" to configure for systems that -do not provide ANSI C function prototypes. This could potentially collide -with other systems using a "__P" macro for similar or different purposes.</p> - <p>The Berkeley DB library needs information about specifically sized types for -each architecture. If they are not provided by the system, they are -typedef'd in the db.h include file. The types that may be typedef'd -by db.h include the following: u_int8_t, int16_t, u_int16_t, int32_t, -u_int32_t, u_char, u_short, u_int, and u_long.</p> - <p>The Berkeley DB library declares a few external routines. All these routines -are prefixed with the strings "db_". All internal Berkeley DB routines are -prefixed with the strings "__XXX_", where "XXX" is the subsystem prefix -(for example, "__db_XXX_" and "__txn_XXX_").</p> + <p> + The Berkeley DB library is careful to avoid C language + programmer name spaces, but there are a few potential + areas for concern, mostly in the Berkeley DB include file + db.h. The db.h include file defines a number of types and + strings. Where possible, all of these types and strings + are prefixed with "DB_" or "db_". There are a few notable + exceptions. + </p> + <p> + The Berkeley DB library uses a macro named "__P" to + configure for systems that do not provide ANSI C function + prototypes. This could potentially collide with other + systems using a "__P" macro for similar or different + purposes. + </p> + <p> + The Berkeley DB library needs information about + specifically sized types for each architecture. If they + are not provided by the system, they are typedef'd in the + db.h include file. The types that may be typedef'd by db.h + include the following: u_int8_t, int16_t, u_int16_t, + int32_t, u_int32_t, u_char, u_short, u_int, and + u_long. + </p> + <p> + The Berkeley DB library declares a few external + routines. All these routines are prefixed with the strings + "db_". All internal Berkeley DB routines are prefixed with + the strings "__XXX_", where "XXX" is the subsystem prefix + (for example, "__db_XXX_" and "__txn_XXX_"). + </p> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> - <h3 class="title"><a id="idp2778712"></a>Filesystem Name Space</h3> + <h3 class="title"><a id="idp2540280"></a>Filesystem Name Space</h3> </div> </div> </div> - <p>Berkeley DB environments create or use some number of files in environment -home directories. These files are named <a class="link" href="env_db_config.html" title="DB_CONFIG configuration file">DB_CONFIG</a>, "log.NNNNN" -(for example, log.0000000003, where the number of digits following the -dot is unspecified), or with the string prefix "__db" (for example, -__db.001). Applications should never create files or databases in -database environment home directories with names beginning with the -characters "log" or "__db".</p> - <p>In some cases, applications may choose to remove Berkeley DB files as part of -their cleanup procedures, using system utilities instead of Berkeley DB -interfaces (for example, using the UNIX rm utility instead of the -<a href="../api_reference/C/envremove.html" class="olink">DB_ENV->remove()</a> method). This is not a problem, as long as applications -limit themselves to removing only files named "__db.###", where "###" -are the digits 0 through 9. Applications should never remove any files -named with the prefix "__db" or "log", other than "__db.###" files.</p> + <p> + Berkeley DB environments create or use some number of + files in environment home directories. These files are + named <a class="link" href="env_db_config.html" title="DB_CONFIG configuration file">DB_CONFIG</a>, + "log.NNNNN" (for example, log.0000000003, where the number + of digits following the dot is unspecified), or with the + string prefix "__db" (for example, __db.001). Applications + should never create files or databases in database + environment home directories with names beginning with the + characters "log" or "__db". + </p> + <p> + In some cases, applications may choose to remove + Berkeley DB files as part of their cleanup procedures, + using system utilities instead of Berkeley DB interfaces + (for example, using the UNIX rm utility instead of the + <a href="../api_reference/C/envremove.html" class="olink">DB_ENV->remove()</a> method). This is not a problem, as long as + applications limit themselves to removing only files named + "__db.###", where "###" are the digits 0 through 9. + Applications should never remove any files named with the + prefix "__db" or "log", other than "__db.###" + files. + </p> </div> </div> <div class="navfooter"> @@ -117,7 +141,8 @@ named with the prefix "__db" or "log", other than "__db.###" files.</p> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Memory-only or Flash configurations</td> + <td width="40%" align="right" valign="top"> Memory-only or Flash + configurations</td> </tr> </table> </div> |