Context Navigation

Changes between Version 3 and Version 4 of Development/CodeConventions

v3	v4
11	11	* We prefer literal tabs at the start of lines instead of hard spaces.
12	12	* Each top-level definition should have a comment explaining what it is for. One liners are fine.
13		* Running comments in the body of functions are encouraged. Write down what you were expecting the code to do when you wrote it, so it reads like a story. Aim for about 1 comment line every 5-10 code lines, depending on how complex the code is.
	13	* Running comments in the bodies of functions are encouraged. Write down what you were expecting the code to do when you wrote it, so it reads like a story. Aim for about 1 comment line every 5-10 code lines, depending on how complex the code is.
14	14
15	15	* If a function does several things in a regular way, then it should look like it in the source code. This means you should line up arguments to similar function calls. For example, use this