6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-01-02 07:32:52 +00:00
Code Issues Projects Releases Wiki Activity

fix some validation problems

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@121444 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner 2010-12-10 00:54:03 +00:00
parent 69ad797214
commit 78ceb3a415
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/CodingStandards.html
View File

@ -60,7 +60,7 @@
loop</a></li> loop</a></li>
<li><a href="#ll_iostream"><tt>#include &lt;iostream&gt;</tt> is <li><a href="#ll_iostream"><tt>#include &lt;iostream&gt;</tt> is
<em>forbidden</em></a></li> <em>forbidden</em></a></li>
<li><a href="#ll_raw_ostream">Use <tt>raw_ostream</tt></a</li> <li><a href="#ll_raw_ostream">Use <tt>raw_ostream</tt></a></li>
<li><a href="#ll_avoidendl">Avoid <tt>std::endl</tt></a></li> <li><a href="#ll_avoidendl">Avoid <tt>std::endl</tt></a></li>
</ol></li> </ol></li>
@ -828,24 +828,25 @@ and <tt>isLValue()</tt>). Different kinds of declarations have different rules:
</p> </p>
<ul> <ul>
<li><b>Type names</b> (including classes, structs, enums, typedefs, etc) should <li><p><b>Type names</b> (including classes, structs, enums, typedefs, etc)
be nouns and start with an upper-case letter (e.g. <tt>TextFileReader</tt>). should be nouns and start with an upper-case letter (e.g.
<tt>TextFileReader</tt>).</p>
</li> </li>
<li><b>Function names</b> should be verb phrases (as they represent <li><p><b>Function names</b> should be verb phrases (as they represent
actions), and command-like function should be imperative. The name should actions), and command-like function should be imperative. The name should
be camel case, and start with a lower case letter (e.g. <tt>openFile()</tt> be camel case, and start with a lower case letter (e.g. <tt>openFile()</tt>
or <tt>isFoo()</tt>). or <tt>isFoo()</tt>).</p>
</li> </li>
<li><b>Enum declarations</b> (e.g. "enum Foo {...}") are types, so they should <li><p><b>Enum declarations</b> (e.g. "enum Foo {...}") are types, so they
follow the naming conventions for types. A common use for enums is as a should follow the naming conventions for types. A common use for enums is as a
discriminator for a union, or an indicator of a subclass. When an enum is discriminator for a union, or an indicator of a subclass. When an enum is
used for something like this, it should have a "Kind" suffix (e.g. used for something like this, it should have a "Kind" suffix (e.g.
"ValueKind"). "ValueKind").</p>
</li> </li>
<li><b>Enumerators</b> (e.g. enum { Foo, Bar }) and <li><p><b>Enumerators</b> (e.g. enum { Foo, Bar }) and
<b>public member variables</b> should start with an upper-case letter, just <b>public member variables</b> should start with an upper-case letter, just
like types. Unless the enumerators are defined in their own small like types. Unless the enumerators are defined in their own small
namespace or inside a class, enumerators should have a prefix corresponding namespace or inside a class, enumerators should have a prefix corresponding