6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-14 11:32:34 +00:00
Code Issues Projects Releases Wiki Activity

Add the common begin/end naming convention to the coding standard.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@187902 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Rafael Espindola 2013-08-07 19:34:37 +00:00
parent ee0dcf4b3e
commit f4c2104d00
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/CodingStandards.rst
View File

@ -796,7 +796,9 @@ In general, names should be in camel case (e.g. ``TextFileReader`` and
As an exception, classes that mimic STL classes can have member names in STL's As an exception, classes that mimic STL classes can have member names in STL's
style of lower-case words separated by underscores (e.g. ``begin()``, style of lower-case words separated by underscores (e.g. ``begin()``,
``push_back()``, and ``empty()``). ``push_back()``, and ``empty()``). Classes that provide multiple
iterators should add a singular prefix to ``begin()`` and ``end()``
(e.g. ``global_begin()`` and ``use_begin()``).
Here are some examples of good and bad names: Here are some examples of good and bad names: