From: daniel_james_at_[hidden]
Date: 2007-11-10 11:06:54
Author: danieljames
Date: 2007-11-10 11:06:54 EST (Sat, 10 Nov 2007)
New Revision: 40993
URL: http://svn.boost.org/trac/boost/changeset/40993
Log:
Fix some of the links in the development requirements page. And use <strong>
instead of <bold>. Still more links to fix. Refs #1357.
Text files modified:
website/public_html/beta/development/requirements.html | 27 +++++++++++++++------------
1 files changed, 15 insertions(+), 12 deletions(-)
Modified: website/public_html/beta/development/requirements.html
==============================================================================
--- website/public_html/beta/development/requirements.html (original)
+++ website/public_html/beta/development/requirements.html 2007-11-10 11:06:54 EST (Sat, 10 Nov 2007)
@@ -243,7 +243,7 @@
Standard Library where applicable.</p>
<p>Headers should be good neighbors. See the <a href=
- "header.html">header policy</a>. See <a href=
+ "/development/header.html">header policy</a>. See <a href=
"#Naming_consistency">Naming consistency</a>.</p>
<p>Follow quality programming practices. See, for example,
@@ -253,13 +253,14 @@
<p>Use the C++ Standard Library or other Boost libraries, but
only when the benefits outweigh the costs. Do not use libraries
other than the C++ Standard Library or Boost. See <a href=
- "library_reuse.html">Library reuse</a>.</p>
+ "/development/reuse.html">Library reuse</a>.</p>
<p>Read Implementation Variation to
see how to supply performance, platform, or other
implementation variations.</p>
- <p>Read the <a href="separate_compilation.html">guidelines for
+ <p>Read the <a href=
+ "/development/separate_compilation.html">guidelines for
libraries with separate source</a> to see how to ensure that
compiled link libraries meet user expectations.</p>
@@ -296,7 +297,7 @@
users can see how to use your library.</p>
<p>Provide a regression test program or programs which follow
- the <a href="test_policy.html">Test Policies and
+ the <a href="/development/test.html">Test Policies and
Protocols</a>.</p>
<p>Although some boost members use proportional fonts, tabs,
@@ -408,16 +409,18 @@
<ul>
<li>File and directory names must contain only
- <b>lowercase</b> ASCII letters, numbers, underscores, and a
- period. Leading character must be alphabetic. Maximum length
- 31. Only a single period is permitted. These requirements
- ensure file and directory names are relatively portable.</li>
+ <strong>lowercase</strong> ASCII letters, numbers,
+ underscores, and a period. Leading character must be
+ alphabetic. Maximum length 31. Only a single period is
+ permitted. These requirements ensure file and directory names
+ are relatively portable.</li>
<li>Files intended to be processed by a C++ compiler as part
- of a translation unit should have <b>a three-letter filename
- extension ending in "pp"</b>. Other files should <i>not</i>
- use extensions ending in "pp". This convention makes it easy
- to identify all of the C++ source in Boost.</li>
+ of a translation unit should have <strong>a three-letter
+ filename extension ending in "pp"</strong>. Other files
+ should <i>not</i> use extensions ending in "pp". This
+ convention makes it easy to identify all of the C++ source in
+ Boost.</li>
<li>All libraries have at their highest level a primary
directory named for the particular library. See <a href=