Software / code / prosody
Changeset
9859:5810f22c4750
Actually remove coding_style.txt
| author | Matthew Wild <mwild1@gmail.com> |
|---|---|
| date | Thu, 14 Mar 2019 16:18:00 +0000 |
| parents | 9858:54147de1d1b1 |
| children | 9860:2cf3dcf93d74 |
| files | doc/coding_style.txt |
| diffstat | 1 files changed, 0 insertions(+), 33 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/coding_style.txt Thu Mar 14 16:13:14 2019 +0000 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,33 +0,0 @@ -This file describes some coding styles to try and adhere to when contributing to this project. -Please try to follow, and feel free to fix code you see not following this standard. - -== Indentation == - - 1 tab indentation for all blocks - -== Spacing == - -No space between function names and parenthesis and parenthesis and parameters: - - function foo(bar, baz) - -Single space between braces and key/value pairs in table constructors: - - { foo = "bar", bar = "foo" } - -== Local variable naming == - -In this project there are many places where use of globals is restricted, and locals used for faster access. - -Local versions of standard functions should follow the below form: - - math.random -> m_random - string.char -> s_char - -== Miscellaneous == - -Single-statement blocks may be written on one line when short - - if foo then bar(); end - -'do' and 'then' keywords should be placed at the end of the line, and never on a line by themself.
