60 lines
1.4 KiB
Plaintext
60 lines
1.4 KiB
Plaintext
============
|
|
Coding Style
|
|
============
|
|
|
|
- Use explicit ``!= NULL``, ``!= 0``, etc. This makes code easier to read
|
|
and remove warnings on some platform. Don't forget SPACES before and
|
|
after the comparison operator.
|
|
|
|
Examples:
|
|
BAD:
|
|
``if (a)``
|
|
BAD:
|
|
``if (a!=NULL)``
|
|
GOOD:
|
|
``if (a != NULL)``
|
|
GOOD:
|
|
``if (a != 0)``
|
|
|
|
- Put figure brackets ``{}`` even if you have only one operator
|
|
in ``if``, ``for``, etc. This also makes code easier to read and
|
|
saves a lot of time when you need to quickly change something.
|
|
|
|
Examples:
|
|
BAD:
|
|
.. line-block::
|
|
|
|
if (a != NULL)
|
|
message(G_LOG_LEVEL_MESSAGE, "Ko");
|
|
GOOD:
|
|
.. line-block::
|
|
|
|
if (a != NULL) {
|
|
message(G_LOG_LEVEL_MESSAGE, "Ok");
|
|
}
|
|
|
|
- Put SPACES before the opening round bracket and after the closing round
|
|
bracket with ``if``, ``for``, ``switch``, ``while``, etc. One more time,
|
|
it improves the readability of the code.
|
|
|
|
Examples:
|
|
BAD:
|
|
.. line-block::
|
|
|
|
if(a != NULL){
|
|
message(G_LOG_LEVEL_MESSAGE, "Ko");
|
|
}
|
|
GOOD:
|
|
.. line-block::
|
|
|
|
if (a != NULL) {
|
|
message(G_LOG_LEVEL_MESSAGE, "Ok");
|
|
}
|
|
|
|
- Check for memory leaks.
|
|
I recommend valgrind (http://valgrind.kde.org) utility with options:
|
|
--leak-check=yes
|
|
--show-reachable=yes
|
|
--num-callers=32
|
|
--suppressions=tests/valgrind/openssl.supp
|