4 Use DEBUG_0() only for temporary debugging i.e. not in code in the repository.
5 The user will then not see irrelevant debug output when the default
6 debug level = 0 is used.
9 If the first word of the message is "error" or "warning" (case insensitive)
10 the message will be color-coded appropriately.
12 --------------------------------------------------------------------------------
14 GPL header, in every file, like this:
17 * \short Short description of this file.
21 * Optionaly detailed description of this file
26 * This file is a part of Geeqie project (http://www.geeqie.org/).
27 * Copyright (C) 2008 - 2016 The Geeqie Team
29 * This program is free software; you can redistribute it and/or modify it
30 * under the terms of the GNU General Public License as published by the Free
31 * Software Foundation; either version 2 of the License, or (at your option)
34 * This program is distributed in the hope that it will be useful, but WITHOUT
35 * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
36 * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
40 --------------------------------------------------------------------------------
44 Start with a short summary in the first line (without a dot at the end) followed
45 by a empty line. Use whole sentences begins with Capital letter. For each
46 modification use new line. Or you can write the theme, colon and then every
47 change on new line, begin with "- ".
49 See also: http://www.tpope.net/node/106
55 There was the bug that something was wrong. I fixed it.
58 - the interface was modified
59 - new functions were added
61 --------------------------------------------------------------------------------
66 Names of variables & functions: small_letters
67 of defines: CAPITAL_LETTERS
69 Try to use explicit variable and function names.
71 Try not to use macros.
72 Use EITHER "struct foo" OR "foo"; never both
90 if (<cond_very_very_very_very_very_very_very_very_very_long> &&
91 <cond2very_very_very_very_very_very_very_very_very_long>)
104 for (i = 0; i <= 10; i++)
114 gint bar(<var_def>, <var_def>, <var_def>)
120 return 0; // i.e. SUCCESS; if error, you must return minus <err_no>
130 Pragma: (Indentation 2 spaces)
134 # define _(String) (String)
135 #endif /* ENABLE_NLS */
141 --------------------------------------------------------------------------------
143 Use spaces around every operator (except ".", "->", "++" and "--");
144 unary operator '*' and '&' are missing the space from right;
145 (and also unary '-').
146 As you can see above, parentheses are closed to inside, i.e. " (blah blah) "
147 In "function(<var>)" there are no space before '('.
148 You MAY use more tabs/spaces than you OUGHT TO (according to this CodingStyle), if
149 it makes your code nicer in being verticaly indented.
150 Variables declarations should be followed by a blank line and should always be
151 at the start of the block.
153 --------------------------------------------------------------------------------
155 Use glib types when possible (ie. gint and gchar instead of int and char).
156 Use glib functions when possible (ie. g_ascii_isspace() instead of isspace()).
157 Check if used functions are not deprecated.
159 --------------------------------------------------------------------------------
163 To document the code use the following rules to allow extraction with doxygen.
164 Do not save with comments. Not all comments have to be doxygen comments.
166 - Use C comments in plain C files and use C++ comments in C++ files for one line
168 - Use '/**' (note the two asterisks) to start comments to be extracted by
169 doxygen and start every following line with " *".
170 - Use '\' to indicate doxygen keywords/commands (see below).
171 - Use the '\deprecated' command to tell if the function is subject to be deleted
172 or to a complete rewrite.
176 To document functions or big structures:
178 * \brief This is a short description of the function.
180 * This function does ...
182 * \param x1 This is the first parameter named x1
183 * \param y1 This is the second parameter named y1
184 * \return What the function returns
185 * You can extend that return description (or anything else) by indenting the
186 * following lines until the next empty line or the next keyword/command.
187 * \see Cross reference
190 To document members of a structure that have to be documented (use it at least
191 for big structures) use the '/**<' format:
192 int counter; /**< This counter counts images */
194 For further documentation about doxygen see
195 http://www.stack.nl/~dimitri/doxygen/manual.html. For the possible commands you
196 can use see http://www.stack.nl/~dimitri/doxygen/commands.html.
198 But in case just think about that the documentation is for other developers not
199 for the end user. So keep the focus.