doc/coding_style.txt

Fri, 28 May 2010 18:01:53 -0400

author
Jeff Mitchell <jeff@jefferai.org>
date
Fri, 28 May 2010 18:01:53 -0400
changeset 3163
20c851616ade
parent 13
716632cca05d
permissions
-rw-r--r--

Add the ability to have names in group files, by putting them with an = sign after the jid:

myname@mydomain.com=My Name

This is then passed on to rosters.

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.

mercurial