Author: dsahlberg
Date: Sat Sep 13 09:05:33 2025
New Revision: 1928406
Log:
In site/trunk:
Continue HTML5 work
* xdocs/versioning.xml
Add missing section id.
Improve consistency of <pre>/<code> elements
* docs/versioning.html
Generated from above
Modified:
apr/site/trunk/docs/versioning.html
apr/site/trunk/xdocs/versioning.xml
Modified: apr/site/trunk/docs/versioning.html
==============================================================================
--- apr/site/trunk/docs/versioning.html Sat Sep 13 08:59:37 2025 (r1928405)
+++ apr/site/trunk/docs/versioning.html Sat Sep 13 09:05:33 2025 (r1928406)
@@ -68,7 +68,7 @@
</div>
<!-- RIGHT SIDE INFORMATION -->
<div id="site-content">
- <div class="h1" id="">
+ <div class="h1" id="numbering">
<h1><strong>APR's Version Numbering</strong></h1>
<blockquote>
<p>This document covers how the APR projects are versioned. Since the APR
@@ -327,12 +327,9 @@ and more complicated depending on what i
<p>Libraries should make their version number available as compile-time
constants. For example:</p>
<blockquote>
- <pre>
- #define FOO_MAJOR_VERSION 1
-
- #define FOO_MINOR_VERSION 4
-
- #define FOO_PATCH_VERSION 0</pre>
+ <pre>#define FOO_MAJOR_VERSION 1
+#define FOO_MINOR_VERSION 4
+#define FOO_PATCH_VERSION 0</pre>
</blockquote>
<p>The above symbols are the minimum required for this specification.</p>
<p>An application that desires, at compile-time, to decide on whether and how
@@ -391,7 +388,7 @@ installation.</p>
<blockquote>
<p>On Unix-ish platforms, the library name should include the <code>MAJOR</code>
version number: </p>
-<blockquote><code>libFOO-MAJOR.so</code></blockquote>
+<blockquote><pre>libFOO-MAJOR.so</pre></blockquote>
<p>This strategy allows an application to explicitly state which version
of the library that it wants to link against. If the application was built for
version 2 of the API, then it can link against <code>libFOO-2.so</code>. If another
@@ -402,8 +399,8 @@ time, both applications' needs can be sa
the <code>.so</code> library to specific versions of that library. For example:
</p>
<blockquote>
- <code>libFOO-MAJOR.so -> libFOO-MAJOR.so.0<br />
- libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</code>
+ <pre>libFOO-MAJOR.so -> libFOO-MAJOR.so.0
+libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</pre>
</blockquote>
<p>In this configuration, applications will be bound to the <code>.so.0</code>
library. The minor version does not come into play here because we want
@@ -422,13 +419,13 @@ specify the <code>MAJOR</code> version n
a subdirectory in some standard location. For example:</p>
<blockquote>
<!-- stupid xemacs mode getting confused by forward slashes... -->
- <code>/usr/include/FOO-MAJOR/</code>
+ <pre>/usr/include/FOO-MAJOR/</pre>
</blockquote>
<p>An application can place the <code>FOO-MAJOR</code> directory on its
include path and include the files normally:</p>
<blockquote>
- <code>#include <FOO-stuff.h><br />
- #include <FOO-more.h></code>
+ <pre>#include <FOO-stuff.h>
+#include <FOO-more.h></pre>
</blockquote>
<p>Depending upon the API that the application is designed to work against, it
can simply include different versions of the include directory.</p>
Modified: apr/site/trunk/xdocs/versioning.xml
==============================================================================
--- apr/site/trunk/xdocs/versioning.xml Sat Sep 13 08:59:37 2025 (r1928405)
+++ apr/site/trunk/xdocs/versioning.xml Sat Sep 13 09:05:33 2025 (r1928406)
@@ -6,7 +6,7 @@
</properties>
<body>
-<section>
+<section id="numbering">
<title>APR's Version Numbering</title>
<p>This document covers how the APR projects are versioned. Since the APR
@@ -282,12 +282,9 @@ and more complicated depending on what i
constants. For example:</p>
<blockquote>
- <pre>
- #define FOO_MAJOR_VERSION 1
-
- #define FOO_MINOR_VERSION 4
-
- #define FOO_PATCH_VERSION 0</pre>
+ <pre>#define FOO_MAJOR_VERSION 1
+#define FOO_MINOR_VERSION 4
+#define FOO_PATCH_VERSION 0</pre>
</blockquote>
<p>The above symbols are the minimum required for this specification.</p>
@@ -355,7 +352,7 @@ installation.</p>
<p>On Unix-ish platforms, the library name should include the <code>MAJOR</code>
version number: </p>
-<blockquote><code>libFOO-MAJOR.so</code></blockquote>
+<blockquote><pre>libFOO-MAJOR.so</pre></blockquote>
<p>This strategy allows an application to explicitly state which version
of the library that it wants to link against. If the application was built for
@@ -369,8 +366,8 @@ the <code>.so</code> library to specific
</p>
<blockquote>
- <code>libFOO-MAJOR.so -> libFOO-MAJOR.so.0<br />
- libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</code>
+ <pre>libFOO-MAJOR.so -> libFOO-MAJOR.so.0
+libFOO-MAJOR.so.0 -> libFOO-MAJOR.so.0.MINOR.PATCH</pre>
</blockquote>
<p>In this configuration, applications will be bound to the <code>.so.0</code>
@@ -393,15 +390,15 @@ a subdirectory in some standard location
<blockquote>
<!-- stupid xemacs mode getting confused by forward slashes... -->
- <code>/usr/include/FOO-MAJOR/</code>
+ <pre>/usr/include/FOO-MAJOR/</pre>
</blockquote>
<p>An application can place the <code>FOO-MAJOR</code> directory on its
include path and include the files normally:</p>
<blockquote>
- <code>#include <FOO-stuff.h><br />
- #include <FOO-more.h></code>
+ <pre>#include <FOO-stuff.h>
+#include <FOO-more.h></pre>
</blockquote>
<p>Depending upon the API that the application is designed to work against, it
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.