svn commit: r816214 - in /websites/staging/httpd/trunk/content: ./ dev/styleguide.html

[bu...@apache.org]

Author: buildbot
Date: Mon May  7 00:26:54 2012
New Revision: 816214

Log:
Staging update by buildbot for httpd

Modified:
    websites/staging/httpd/trunk/content/   (props changed)
    websites/staging/httpd/trunk/content/dev/styleguide.html

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon May  7 00:26:54 2012
@@ -1 +1 @@
-1334843
+1334844

Modified: websites/staging/httpd/trunk/content/dev/styleguide.html
==============================================================================
--- websites/staging/httpd/trunk/content/dev/styleguide.html (original)
+++ websites/staging/httpd/trunk/content/dev/styleguide.html Mon May  7 00:26:54 2012
@@ -120,12 +120,12 @@ the <code>*</code> character (<em>e.g.</
 of "<code>(char*)i</code>")</li>
 </ul>
 <h1 id="details-and-examples">Details and Examples</h1>
-<ol>
+<ul>
 <li><strong>Indentation, General Style</strong> 
 Each level of indentation of code is four spaces. Tab characters should
 never be used. Specific indentation rules for function declarations and
 control-flow keywords are given below.</li>
-</ol>
+</ul>
 <p>Example:</p>
 <div class="codehilite"><pre><span class="n">main</span><span class="p">(</span><span class="nb">int</span> <span class="n">argc</span><span class="p">,</span> <span class="n">char</span> <span class="o">**</span><span class="n">argc</span><span class="p">)</span>
 <span class="p">{</span>
@@ -157,12 +157,12 @@ atomic as possible, and place Boolean op
 </pre></div>
 
 
-<ol>
+<ul>
 <li><strong>Comments</strong> 
 Provide comments which explain the function of code where it is not clear
 from the code itself. Provide rationale where necessary for particular bits
 of code.</li>
-</ol>
+</ul>
 <p>Comments should be indented to same level as the surrounding text.</p>
 <p>Example:</p>
 <div class="codehilite"><pre><span class="n">code</span><span class="p">;</span>
@@ -171,10 +171,10 @@ of code.</li>
 </pre></div>
 
 
-<ol>
+<ul>
 <li><strong>Function Declaration and Layout</strong> 
 Functions are laid out as follows:</li>
-</ol>
+</ul>
 <p>Example:</p>
 <div class="codehilite"><pre><span class="nb">int</span> <span class="n">main</span><span class="p">(</span><span class="nb">int</span> <span class="n">argc</span><span class="p">,</span> <span class="n">char</span> <span class="o">**</span><span class="n">argv</span><span class="p">)</span>
 <span class="p">{</span>
@@ -192,11 +192,11 @@ of the return type text. The code is ind
 closing brace is indented to line up with the opening brace. <strong>Also see the
 section on indenting<A HREF="#long-exps">long declarations and
 invocations</A>.</strong> </p>
-<ol>
+<ul>
 <li><strong>Function Calls</strong> 
 Space after commas in function calls. No space between function name and
 opening bracket.</li>
-</ol>
+</ul>
 <p>Example:</p>
 <div class="codehilite"><pre><span class="n">f</span><span class="p">(</span><span class="n">a</span><span class="p">,</span> <span class="n">b</span><span class="p">);</span>
 </pre></div>
@@ -204,12 +204,12 @@ opening bracket.</li>
 
 <p><strong>Also see the section on indenting<A HREF="#long-exps">long declarations
 and invocations</A>.</strong> </p>
-<ol>
+<ul>
 <li><strong>Flow-Control Layout</strong> 
 Flow-control statements
 (<code>if</code>, <code>while</code>, <code>for</code>, <em>etc.</em>) are
 laid out as in this</li>
-</ol>
+</ul>
 <p>Example:</p>
 <div class="codehilite"><pre><span class="k">if</span> <span class="p">(</span><span class="n">expr</span><span class="p">)</span> <span class="p">{</span>
     <span class="n">code</span><span class="p">;</span>
@@ -227,21 +227,21 @@ brace. If an <code>else</code> clause is
 placed on the line following the closing brace and is indented to line up
 with the corresponding <code>if</code>. <strong>Also see the section on
 indenting<A HREF="#long-exps">long expressions</A>.</strong> </p>
-<ol>
+<ul>
 <li><strong><code>for</code> Layout</strong> 
 Space after the semi-colons.</li>
-</ol>
+</ul>
 <p>Example:</p>
 <div class="codehilite"><pre><span class="k">for</span> <span class="p">(</span><span class="n">a</span><span class="p">;</span> <span class="n">b</span><span class="p">;</span> <span class="n">c</span><span class="p">)</span>
 </pre></div>
 
 
-<ol>
+<ul>
 <li><strong><code>switch</code> Layout</strong> 
 <code>case</code> lines within a <code>switch()</code> are indented to same
 level as the switch statement itself. The code for each case is indented by
 four spaces. Braces are laid out as for other control-flow keywords.</li>
-</ol>
+</ul>
 <p>Example:</p>
 <div class="codehilite"><pre><span class="n">switch</span> <span class="p">(</span><span class="n">x</span><span class="p">)</span> <span class="p">{</span>
 <span class="k">case</span> <span class="n">a:</span>
@@ -252,11 +252,11 @@ four spaces. Braces are laid out as for 
 </pre></div>
 
 
-<ol>
+<ul>
 <li><strong>Expressions</strong> 
 Space before and after assignment and other and operators. No space between
 unary operators (increment, decrement, and negation) and the lvalue.</li>
-</ol>
+</ul>
 <p>Examples:</p>
 <div class="codehilite"><pre><span class="n">a</span> <span class="o">=</span> <span class="n">b</span>
 <span class="n">a</span> <span class="o">+</span> <span class="n">b</span>
@@ -267,10 +267,10 @@ unary operators (increment, decrement, a
 </pre></div>
 
 
-<ol>
+<ul>
 <li><strong>Capitalisation of Enums</strong> 
 No rule.</li>
-</ol>
+</ul>
             
 
             <!-- FOOTER -->