summaryrefslogtreecommitdiff
path: root/CODING
diff options
context:
space:
mode:
authorDave Andreoli <dave@gurumeditation.it>2015-02-16 20:38:25 +0100
committerDave Andreoli <dave@gurumeditation.it>2015-02-16 20:38:25 +0100
commitb4fcee3de22092d206747ba03275833917e9bbdb (patch)
tree2c87b080b8aa83a8c5ef820808fd55844b2db321 /CODING
parenta90f1dd54d313500d9f8e133e6e28f7bc743434e (diff)
Use consistent indentation style with the rest of the code
Diffstat (limited to 'CODING')
-rw-r--r--CODING14
1 files changed, 14 insertions, 0 deletions
diff --git a/CODING b/CODING
index a5c4600..1e4f965 100644
--- a/CODING
+++ b/CODING
@@ -8,6 +8,20 @@ Style
8* When comparing C pointers with NULL, use == and != instead of the python 8* When comparing C pointers with NULL, use == and != instead of the python
9 operator "is". This makes a visual distinction between python and C code. 9 operator "is". This makes a visual distinction between python and C code.
10 10
11* For long lines that do not fit in the 80 cols please use only the first
12 raccomandation from PEP-8 (Aligned with opening delimiter). Example:
13 Yes:
14 foo = long_function_name(var_one, var_two,
15 var_three, var_four)
16 No:
17 foo = long_function_name(
18 var_one, var_two,
19 var_three, var_four)
20
21 This to keep new code consistent with the rest of the bindings and to
22 try to match the style of the C efl code style as much as possible.
23 ...also because I found it more readable and I like it more :P -davemds-
24
11 25
12Design patterns 26Design patterns
13=============== 27===============