# HG changeset patch # User Matthew Wild # Date 1219698407 -3600 # Node ID 716632cca05d71d1456af42af6ae9a4f96abbd62 # Parent 90f22275f7aedcc7524f1c7563d2c5b54d2cdf85 Coding style doc, HACKERS file diff -r 90f22275f7ae -r 716632cca05d HACKERS --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/HACKERS Mon Aug 25 22:06:47 2008 +0100 @@ -0,0 +1,7 @@ +Welcome hackers! + +This project accepts and *encourages* contributions. If you would like to get involved you can join us on our mailing list at: + +You can also find us in the chatroom at lxmppd@chatbox.heavy-horse.co.uk + +Patches are welcome, though before sending we would appreciate if you read docs/coding_style.txt for guidelines on how to format your code. diff -r 90f22275f7ae -r 716632cca05d doc/coding_style.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/doc/coding_style.txt Mon Aug 25 22:06:47 2008 +0100 @@ -0,0 +1,33 @@ +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.