Software /
code /
prosody
File
doc/coding_style.txt @ 6187:c0b4b5d41e55
plugins/muc/muc.lib: Improve set affiliation logic;
- Each affiliation and role is now ranked
- Changes up in affiliation will not downgrade your role
- Now sends a new set of presences if you gained moderator in a semi-anonymous room.
- Better input validation; matches closer with ':set_role'
- Don't short circuit; as if user has non-default role they will not get updated
author | daurnimator <quae@daurnimator.com> |
---|---|
date | Fri, 28 Mar 2014 17:58:25 -0400 |
parent | 13:716632cca05d |
child | 8728:41c959c5c84b |
line wrap: on
line source
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 paramters: 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.