forked from lda/telodendria
Add variable conventions to style guide
This commit is contained in:
parent
a658aef550
commit
335e35a99c
1 changed files with 6 additions and 2 deletions
|
@ -468,7 +468,7 @@ If—after you've reached out to
|
|||
<code>#telodendria-general:bancino.net</code>—it has been
|
||||
determined that there is a problem with <b>Telodendria</b>, it should
|
||||
be reported to <code>#telodendria-issues:bancino.net</code>. There it
|
||||
can be discussed further. The issues channel serves as the official
|
||||
can be discussed further. The issues room serves as the official
|
||||
issue tracker of <b>Telodendria</b>; although severe issues may be copied
|
||||
into a <code>TODO</code> file in the CVS repository just so they
|
||||
don't get lost.
|
||||
|
@ -521,6 +521,10 @@ All function, enumeration, structure, and header names are
|
|||
because it is more compact.
|
||||
</li>
|
||||
<li>
|
||||
All variable names are <code>lowerCamelCase</code>. This is preferred
|
||||
to <code>snake_case</code> because it is more compact.
|
||||
</li>
|
||||
<li>
|
||||
<code>enum</code>s and <code>struct</code>s are always
|
||||
<code>typedef</code>-ed to their same name. The <code>typedef</code>
|
||||
occurs in the public API header, and the actual declaration occurs in
|
||||
|
|
Loading…
Reference in a new issue