<html>
<head>
<base href="https://wiki.asterisk.org/wiki">
<link rel="stylesheet" href="/wiki/s/2030/1/7/_/styles/combined.css?spaceKey=TOP&forWysiwyg=true" type="text/css">
</head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="https://wiki.asterisk.org/wiki/display/TOP/Style+Guide">Style Guide</a></h2>
<h4>Page <b>edited</b> by <a href="https://wiki.asterisk.org/wiki/display/~kpfleming">Kevin P. Fleming</a>
</h4>
<div id="versionComment">
<b>Comment:</b>
C++ style guide edits<br />
</div>
<br/>
<h4>Changes (16)</h4>
<div id="page-diffs">
<table class="diff" cellpadding="0" cellspacing="0">
<tr><td class="diff-snipped" >...<br></td></tr>
<tr><td class="diff-unchanged" ># Empty definitions will be shown by opening and closing braces at the end of the line. <br># Slice file names will end with "If.ice" (where If is for interface) so that developers in IDEs will be able to tell when they were produced generated code. (The Slice translators use the .ice filename as the basis for the generated C++ and C# filenames.) <br></td></tr>
<tr><td class="diff-changed-lines" ># <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">*#pragma once*</span> <span class="diff-added-words"style="background-color: #dfd;">{{#pragma once}}</span> will be used for multiple-include protection. The Slice translators use the MCPP library for C-style preprocessing, which supports <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">*#pragma once*.</span> <span class="diff-added-words"style="background-color: #dfd;">{{#pragma once}}.</span> It provides a performance benefit over traditional <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">*#ifdef*-based</span> <span class="diff-added-words"style="background-color: #dfd;">{{#ifdef}}-based</span> include guards in addition to being easier to read and maintain. <br></td></tr>
<tr><td class="diff-unchanged" > <br> <br></td></tr>
<tr><td class="diff-snipped" >...<br></td></tr>
<tr><td class="diff-unchanged" >|{center}*Figure 1. Slice Example - TimeIf.ice*{center}| <br> <br></td></tr>
<tr><td class="diff-changed-lines" >h4. <span class="diff-changed-words">C<span class="diff-added-chars"style="background-color: #dfd;">\</span>+<span class="diff-added-chars"style="background-color: #dfd;">\</span>+</span> Style Guide <br></td></tr>
<tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">To insure compatibility with gcc, all C++ source and header files must end with a blank line. <br></td></tr>
<tr><td class="diff-added-lines" style="background-color: #dfd;">To ensure compatibility with GCC, all C\+\+ source and header files must end with a newline. <br></td></tr>
<tr><td class="diff-unchanged" > <br></td></tr>
<tr><td class="diff-changed-lines" ># In pointer and reference declarations, the {{&}} and {{*}} <span class="diff-added-words"style="background-color: #dfd;">modifiers</span> should be next to the type, not the variable ({{Foo& foo}}) <br></td></tr>
<tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;"># When declaring {{const}} pointer and references, the {{const}} modifier should be to the left of the type ({{const Foo& foo}}). <br></td></tr>
<tr><td class="diff-added-lines" style="background-color: #dfd;"># When declaring variables, modifiers (such as {{const}} and {{auto}}) should be to written on the left side of the type ({{const Foo& foo}}). <br></td></tr>
<tr><td class="diff-unchanged" > <br></td></tr>
<tr><td class="diff-changed-lines" >h6. <span class="diff-changed-words">C<span class="diff-added-chars"style="background-color: #dfd;">\</span>+<span class="diff-added-chars"style="background-color: #dfd;">\</span>+</span> Header Files <br></td></tr>
<tr><td class="diff-unchanged" >The following additional guidelines will apply to C++ header files: <br></td></tr>
<tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;"># *#pragma once* will be used for multiple-include protection. *#pragma once* has been supported in GCC since version 3.4.0, and in Visual Studio since (at least) version 6. In addition, it provides a performance benefit over traditional *#ifdef*-based include guards in addition to being easier to read and maintain. <br># Forward references for types whose definitions can be deferred will be used to reduce including additional files when practical. For example, when only a pointer or reference to a type is required, the full definition of the type is not necessary. (But header files should be usable without requiring the .CPP file to include additional files.) <br># Avoid "using namespace" in header files, which could flatten the namespace inadvertently for many other modules. <br># Use lower-case "m" prefix (for member) for member variables, to avoid hiding member variable with local variables in methods. This is not done for Slice class member variables, as Slice class members are always public, and more analogous to a C++ struct than a C++ class. <br></td></tr>
<tr><td class="diff-added-lines" style="background-color: #dfd;"># {{#pragma once}} will be used for multiple-include protection. {{#pragma once}} has been supported in GCC since version 3.4.0, and in Visual Studio since (at least) version 6. It provides a performance benefit over traditional {{#ifdef}}-based include guards in addition to being easier to read and maintain. <br># Forward declarations should be used when the code does not need the entire type declaration; the most common cases of this are pointer and reference variables, which only need the type name declared, but not its complete declaration. <br># Header files should {{#include}} all other headers required to compile them; source files that *#include* a header file should not be required to know which other headers are required for it. <br># Avoid {{using namespace;}} in header files, which could pollute the namespace inadvertently for modules which include that header file. <br># Use lower-case "m" prefix (_member_) for member variables, to avoid hiding member variables with local variables in methods. This is not done for Slice class member variables, as Slice class members are always public, since Slice classes are more analogous to C\+\+ {{struct}} than C\+\+ {{class}}. <br></td></tr>
<tr><td class="diff-unchanged" > <br> <br></td></tr>
<tr><td class="diff-snipped" >...<br></td></tr>
<tr><td class="diff-unchanged" > <br> <br></td></tr>
<tr><td class="diff-changed-lines" >h6. <span class="diff-changed-words">C<span class="diff-added-chars"style="background-color: #dfd;">\</span>+<span class="diff-added-chars"style="background-color: #dfd;">\</span>+</span> Source Files <br></td></tr>
<tr><td class="diff-changed-lines" >The following style guidelines will apply to <span class="diff-changed-words">C<span class="diff-added-chars"style="background-color: #dfd;">\</span>+<span class="diff-added-chars"style="background-color: #dfd;">\</span>+</span> source (.cpp) files: <br></td></tr>
<tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;"># Organize include statements into blocks based on level. Highest level includes first, specific packages, and finally our own. <br># Flatten namespaces (if desired for convenience) here in the CPP file rather than in the headers. <br></td></tr>
<tr><td class="diff-added-lines" style="background-color: #dfd;"># Organize {{#include}} statements into blocks based on level. System-level headers first, library headers next (Boost, PJSIP, etc.), Asterisk SCF API headers next, and finally local headers. <br># Flatten namespaces (if desired for convenience) here in the source file, not in header files. <br></td></tr>
<tr><td class="diff-unchanged" > <br>|!StyleGuides-CppFile.png|border=1!| <br></td></tr>
<tr><td class="diff-changed-lines" >|{center}*Figure 1. <span class="diff-changed-words">C<span class="diff-added-chars"style="background-color: #dfd;">\</span>+<span class="diff-added-chars"style="background-color: #dfd;">\</span>+</span> Source Example*{center}| <br></td></tr>
<tr><td class="diff-unchanged" > <br>h4. Editor setup <br></td></tr>
<tr><td class="diff-snipped" >...<br></td></tr>
<tr><td class="diff-unchanged" > <br>{note} <br></td></tr>
<tr><td class="diff-changed-lines" >Various flavors of <span class="diff-changed-words"><span class="diff-deleted-chars"style="color:#999;background-color:#fdd;text-decoration:line-through;">e</span><span class="diff-added-chars"style="background-color: #dfd;">E</span>macs</span> store startup scripts in different places. Check the documentation for your distribution if .emacs doesn't seem quite right for you. <br></td></tr>
<tr><td class="diff-unchanged" >{note} <br> <br></td></tr>
<tr><td class="diff-snipped" >...<br></td></tr>
</table>
</div> <h4>Full Content</h4>
<div class="notificationGreySide">
<div class='panelMacro'><table class='infoMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/wiki/images/icons/emoticons/information.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td>This page defines a Style Guide for developing Slice and C++ source code.</td></tr></table></div>
<div>
<ul>
<li><a href='#StyleGuide-CommonRules'>Common Rules</a></li>
<li><a href='#StyleGuide-SliceStyleGuide'>Slice Style Guide</a></li>
<li><a href='#StyleGuide-C%5C%5CStyleGuide'>C++ Style Guide</a></li>
<ul>
<li><a href='#StyleGuide-C%5C%5CHeaderFiles'>C++ Header Files</a></li>
<li><a href='#StyleGuide-C%5C%5CSourceFiles'>C++ Source Files</a></li>
</ul>
<li><a href='#StyleGuide-Editorsetup'>Editor setup</a></li>
<ul>
<li><a href='#StyleGuide-Emacs'>Emacs</a></li>
</ul>
</ul></div>
<h4><a name="StyleGuide-CommonRules"></a>Common Rules</h4>
<p>The following style guidelines will be followed for both Slice and C++ code:</p>
<p> <b>C1.</b> Braces for compound statements will be on their own lines, at the same indentation level as the statement they are part of. Statements in the brace-enclosed block will be indented one level from the braces. The only exception to this rule is for C++ namespace and Slice module blocks; because the nesting of these scopes could change in the future, if indentation was used it would have to be changed across many source files if the nesting changed. In addition, most code is contained in at least three namespaces/modules, if not more, and indenting the code to represent this would waste a great deal of space and make the code harder to read.<br/>
<b>C2.</b> Indentation: 4 spaces per level, no tabs.<br/>
<b>C3.</b> Interface, class and structure names will be in UpperCamelCase style. <br/>
<b>C4.</b> Function, operation and member variable names will follow lowerCamelCase style.<br/>
<b>C5.</b> Comments will follow Doxygen (Javadoc form) guidelines. For Slice this will apply to interface, class and struct definitions, and all operations. For C++, this will apply to classes and operations. All other comments will follow C++ standard convention, which is for "//" comments to be used except for lengthy multi-line comments. <br/>
<b>C6.</b> Comment the end of namespace scopes (or any code blocks long enough that would likely not be entirely visible on a typical screen) to improve maintainability / readability. <br/>
<b>C7.</b> All comments shall be in the English language.</p>
<h4><a name="StyleGuide-SliceStyleGuide"></a>Slice Style Guide</h4>
<p>The following additional style guidelines will be followed in development of Asterisk SCF Slice definitions:</p>
<ol>
<li>Empty definitions will be shown by opening and closing braces at the end of the line.</li>
<li>Slice file names will end with "If.ice" (where If is for interface) so that developers in IDEs will be able to tell when they were produced generated code. (The Slice translators use the .ice filename as the basis for the generated C++ and C# filenames.)</li>
<li><tt>#pragma once</tt> will be used for multiple-include protection. The Slice translators use the MCPP library for C-style preprocessing, which supports <tt>#pragma once</tt>. It provides a performance benefit over traditional <tt>#ifdef</tt>-based include guards in addition to being easier to read and maintain.</li>
</ol>
<div class='table-wrap'>
<table class='confluenceTable'><tbody>
<tr>
<td class='confluenceTd'><span class="image-wrap" style=""><img src="/wiki/download/attachments/3702855/StyleGuides-Slice.png?version=4&modificationDate=1291244720178" style="border: 1px solid black" /></span></td>
</tr>
<tr>
<td class='confluenceTd'><div class="" align="center"><b>Figure 1. Slice Example - TimeIf.ice</b></div>
</td>
</tr>
</tbody></table>
</div>
<h4><a name="StyleGuide-C%5C%5CStyleGuide"></a>C++ Style Guide</h4>
<p>To ensure compatibility with GCC, all C++ source and header files must end with a newline.</p>
<ol>
<li>In pointer and reference declarations, the <tt>&</tt> and <tt>*</tt> modifiers should be next to the type, not the variable (<tt>Foo& foo</tt>)</li>
<li>When declaring variables, modifiers (such as <tt>const</tt> and <tt>auto</tt>) should be to written on the left side of the type (<tt>const Foo& foo</tt>).</li>
</ol>
<h6><a name="StyleGuide-C%5C%5CHeaderFiles"></a>C++ Header Files</h6>
<p>The following additional guidelines will apply to C++ header files:</p>
<ol>
<li><tt>#pragma once</tt> will be used for multiple-include protection. <tt>#pragma once</tt> has been supported in GCC since version 3.4.0, and in Visual Studio since (at least) version 6. It provides a performance benefit over traditional <tt>#ifdef</tt>-based include guards in addition to being easier to read and maintain.</li>
<li>Forward declarations should be used when the code does not need the entire type declaration; the most common cases of this are pointer and reference variables, which only need the type name declared, but not its complete declaration.</li>
<li>Header files should <tt>#include</tt> all other headers required to compile them; source files that <b>#include</b> a header file should not be required to know which other headers are required for it.</li>
<li>Avoid <tt>using namespace;</tt> in header files, which could pollute the namespace inadvertently for modules which include that header file.</li>
<li>Use lower-case "m" prefix (<em>member</em>) for member variables, to avoid hiding member variables with local variables in methods. This is not done for Slice class member variables, as Slice class members are always public, since Slice classes are more analogous to C++ <tt>struct</tt> than C++ <tt>class</tt>.</li>
</ol>
<div class='table-wrap'>
<table class='confluenceTable'><tbody>
<tr>
<td class='confluenceTd'><span class="image-wrap" style=""><img src="/wiki/download/attachments/3702855/StyleGuides-Header.png?version=5&modificationDate=1291244917853" style="border: 1px solid black" /></span></td>
</tr>
<tr>
<td class='confluenceTd'><div class="" align="center"><b>Figure 1. C++ Header Example</b></div>
</td>
</tr>
</tbody></table>
</div>
<h6><a name="StyleGuide-C%5C%5CSourceFiles"></a>C++ Source Files</h6>
<p>The following style guidelines will apply to C++ source (.cpp) files:</p>
<ol>
<li>Organize <tt>#include</tt> statements into blocks based on level. System-level headers first, library headers next (Boost, PJSIP, etc.), Asterisk SCF API headers next, and finally local headers.</li>
<li>Flatten namespaces (if desired for convenience) here in the source file, not in header files.</li>
</ol>
<div class='table-wrap'>
<table class='confluenceTable'><tbody>
<tr>
<td class='confluenceTd'><span class="image-wrap" style=""><img src="/wiki/download/attachments/3702855/StyleGuides-CppFile.png?version=5&modificationDate=1291245050440" style="border: 1px solid black" /></span></td>
</tr>
<tr>
<td class='confluenceTd'><div class="" align="center"><b>Figure 1. C++ Source Example</b></div>
</td>
</tr>
</tbody></table>
</div>
<h4><a name="StyleGuide-Editorsetup"></a>Editor setup</h4>
<h6><a name="StyleGuide-Emacs"></a>Emacs</h6>
<p>Save a copy of the attached file <tt><a href="/wiki/download/attachments/3702855/asterisk-scf-style.el?version=2&modificationDate=1291219045376">asterisk-scf-style.el</a></tt> into your <tt>site-lisp</tt> directory. Make sure you have the following in your <tt>.emacs</tt> files.</p>
<div class='panelMacro'><table class='noteMacro'><colgroup><col width='24'><col></colgroup><tr><td valign='top'><img src="/wiki/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt="" border="0"></td><td>Various flavors of Emacs store startup scripts in different places. Check the documentation for your distribution if .emacs doesn't seem quite right for you.</td></tr></table></div>
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>(require 'asterisk-scf-style)
;; Treat .h files as C++ files
(add-to-list 'auto-mode-alist '("\\.h\\'" . c++-mode))
;; You may want to merge this with existing configuration in your custom-set-variables block
(setq indent-tabs-mode nil
require-final-newline t
show-trailing-whitespace t
c-default-style '((c-mode . "asterisk-scf") (c++-mode . "asterisk-scf"))
)
</pre>
</div></div>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;">
<a href="https://wiki.asterisk.org/wiki/users/viewnotifications.action" class="grey">Change Notification Preferences</a>
</div>
<a href="https://wiki.asterisk.org/wiki/display/TOP/Style+Guide">View Online</a>
|
<a href="https://wiki.asterisk.org/wiki/pages/diffpagesbyversion.action?pageId=3702855&revisedVersion=37&originalVersion=36">View Changes</a>
|
<a href="https://wiki.asterisk.org/wiki/display/TOP/Style+Guide?showComments=true&showCommentArea=true#addcomment">Add Comment</a>
</div>
</div>
</div>
</div>
</div>
</body>
</html>