[glib-networking/mcatanzaro/hacking] Add HACKING.md to document code style rules
- From: Michael Catanzaro <mcatanzaro src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib-networking/mcatanzaro/hacking] Add HACKING.md to document code style rules
- Date: Tue, 25 Jun 2019 01:21:57 +0000 (UTC)
commit 75bb28b9cdabc167629457d2f1bf1178cadf54db
Author: Michael Catanzaro <mcatanzaro igalia com>
Date: Mon Jun 24 20:19:22 2019 -0500
Add HACKING.md to document code style rules
This is very very basic as of yet, but maybe we will add more rules over
time.
HACKING.md | 40 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 40 insertions(+)
---
diff --git a/HACKING.md b/HACKING.md
new file mode 100644
index 0000000..bb61723
--- /dev/null
+++ b/HACKING.md
@@ -0,0 +1,40 @@
+# Code Style
+
+In order to keep the code nice and clean we have a few requirements you'll
+need to stick to in order to get your patch accepted:
+
+ * Use GNU-style indentation:
+
+ ```
+ if (condition)
+ {
+ // body
+ }
+ ```
+
+ * No braces for one line control clauses except when another clause in the
+ chain contains more than one line.
+
+ * Callback functions have a suffix _cb. TODO: ensure existing code follows this
+ rule.
+
+ * Use `char`/`int`/`double`/…, not `gchar`/`gint`/`gdouble`/… types, except
+ when implementing GLib vfuncs that use these types. TODO: ensure existing
+ code follows this rule.
+
+ * All implementation files must include first `"config.h"`, followed by
+ the primary header, followed by a blank line, followed by all the
+ local headers sorted alphabetically, followed by a blank line,
+ followed by all the system headers sorted alphabetically. Headers
+ should follow the same pattern excluding the config.h and
+ self file section, for obvious reasons. TODO: ensure existing code follows
+ this rule.
+
+ * There's no space between a type cast and the variable name: Right:
+ `(int *)foo`. Wrong: `(int*) foo`.
+
+ * Avoid explicit comparisons against TRUE, FALSE, and NULL. Right:
+ `if (!condition)`, `if (!pointer)`, `if (integer == 0)`. Wrong:
+ `if (condition == FALSE)`, `if (pointer == NULL)`, `if (!integer)`.
+ Exception: `pointer != NULL` may be used to convert to gboolean since some
+ developers find this more natural than `!!pointer`.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]