Contributing - Revision history

It9999: /* Code */

2012-10-15T06:12:15Z

‎Code

Hirato: /* Style */

2011-12-13T05:45:36Z

‎Style

Mike: Protected "Contributing" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2011-08-19T21:02:12Z

Protected "Contributing" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

Chocolatepie33: /* Testing */

2011-08-01T23:57:15Z

‎Testing

Ramon turner at 10:33, 30 June 2011

2011-06-30T10:33:17Z

@@ Line 10: / Line 10: @@
 If you lack any ideas of what to implement, should you wish to contribute in this way, there are various todo lists that should help you out
 * http://www.svn.kids.platinumarts.net/32pas32/trunk/src/rpggame/rpgtodo.txt
 * http://www.svn.kids.platinumarts.net/32pas32/trunk/src/sspgame/ssptodo.txt

@@ Line 19: / Line 19: @@
 The files in the engine and the respective game modules use slightly differing styles... The easiest way is simply to remain consistent with the style present in the file.
-===Braces===
+For more detailed information, see [[Coding Style]]
-−
-Braces are not indented and are to be placed on a new line (unless the statement in question is a one liner). Braces are not required inside switch statements. They are not required after if's or else's either, PROVIDED there's only 1 statement following their invocation.
-−
-===Indents===
-−
-Indents are done either via Tabulators or 4 spaces. Make sure you know which style the files use, and that your text editor currently uses that style before modifying them. Hirato uses a size of 8 spaces for the Tabulators, mimicking him might help you identify the style in the files.
-−
-'''things to indent'''
-* The body within braces
-* cases within a switch
-* any lines beyond the first of a macro
-* items after their respective if and else statements
-−
-===One-liners===
-−
-One liners are permitted, but only if they are short small and simple. If the length is in excess of 30 characters, you should consider just expanding it out instead.
-−
-===Pointers===
-−
-To help ease confusion, pointers are written C style. That is next to the variable name (char *string) instead of next to the type (char* string).
-To those not in the know, char* string1, string2; does not declare two pointers, but a pointer and a character.
-−
-===Whitespace===
-−
-when declaring functions, there must be 1 empty line of whitespace between the end of the prior definition and the beginning of the new one. Variables and prototype definitions may be declared without any whitespace between each declaration. Provided they are grouped sensibly. It's recommended that the code also be grouped into 2-10 line blocks which concentrate on a certain aspect to help with readability. A series of one liners may also be grouped without spaces between.
 ==licensing==

← Older revision		Revision as of 23:57, 1 August 2011
Line 73:		Line 73:
	* [[Development]]		* [[Development]]
	* [[Bug reports]]		* [[Bug reports]]
−	~~[http://essaywritingservices.org/prices.php write my paper]~~

← Older revision		Revision as of 10:33, 30 June 2011
Line 73:		Line 73:
	* [[Development]]		* [[Development]]
	* [[Bug reports]]		* [[Bug reports]]
		+	[http://essaywritingservices.org/prices.php write my paper]

← Older revision	Revision as of 21:02, 19 August 2011
(No difference)