httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r816215 - in /websites/staging/httpd/trunk/content: ./ dev/styleguide.html
Date Mon, 07 May 2012 00:30:32 GMT
Author: buildbot
Date: Mon May  7 00:30:31 2012
New Revision: 816215

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:30:31 2012
@@ -1 +1 @@
-1334844
+1334845

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:30:31 2012
@@ -121,11 +121,11 @@ of "<code>(char*)i</code>")</li>
 </ul>
 <h1 id="details-and-examples">Details and Examples</h1>
 <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>
+<li><strong>Indentation, General Style</strong></li>
 </ul>
+<p>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.</p>
 <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>
@@ -158,11 +158,11 @@ atomic as possible, and place Boolean op
 
 
 <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>
+<li><strong>Comments</strong> </li>
 </ul>
+<p>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.</p>
 <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>
@@ -172,9 +172,9 @@ of code.</li>
 
 
 <ul>
-<li><strong>Function Declaration and Layout</strong> 
-Functions are laid out as follows:</li>
+<li><strong>Function Declaration and Layout</strong> </li>
 </ul>
+<p>Functions are laid out as follows:</p>
 <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>
@@ -193,10 +193,10 @@ closing brace is indented to line up wit
 section on indenting<A HREF="#long-exps">long declarations and
 invocations</A>.</strong> </p>
 <ul>
-<li><strong>Function Calls</strong> 
-Space after commas in function calls. No space between function name and
-opening bracket.</li>
+<li><strong>Function Calls</strong> </li>
 </ul>
+<p>Space after commas in function calls. No space between function name and
+opening bracket.</p>
 <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>
@@ -205,11 +205,11 @@ opening bracket.</li>
 <p><strong>Also see the section on indenting<A HREF="#long-exps">long declarations
 and invocations</A>.</strong> </p>
 <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>
+<li><strong>Flow-Control Layout</strong> </li>
 </ul>
+<p>Flow-control statements
+(<code>if</code>, <code>while</code>, <code>for</code>,
<em>etc.</em>) are
+laid out as in this</p>
 <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>
@@ -228,9 +228,9 @@ placed on the line following the closing
 with the corresponding <code>if</code>. <strong>Also see the section on
 indenting<A HREF="#long-exps">long expressions</A>.</strong> </p>
 <ul>
-<li><strong><code>for</code> Layout</strong> 
-Space after the semi-colons.</li>
+<li><strong><code>for</code> Layout</strong> </li>
 </ul>
+<p>Space after the semi-colons.</p>
 <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>
@@ -253,10 +253,10 @@ four spaces. Braces are laid out as for 
 
 
 <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>
+<li><strong>Expressions</strong> </li>
 </ul>
+<p>Space before and after assignment and other and operators. No space between
+unary operators (increment, decrement, and negation) and the lvalue.</p>
 <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>
@@ -268,9 +268,9 @@ unary operators (increment, decrement, a
 
 
 <ul>
-<li><strong>Capitalisation of Enums</strong> 
-No rule.</li>
+<li><strong>Capitalisation of Enums</strong> </li>
 </ul>
+<p>No rule.</p>
             
 
             <!-- FOOTER -->



Mime
View raw message