1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
|
======================
Programming guidelines
======================
NAVIT is a team-project, thus a lot of coders are working on it's development and code base.
To get a unified coding style and make it easier for everybody to work with parts, that someone else wrote, we tried to specify the formatting of our source and how we deal with third party modules as following.
Enforced guidelines via CircleCI
================================
The 1st step of the checks enforced after a PR is created or updated is what we call "sanity checks".
Those enforce the coding style for our C and Java files. During this phase we have several steps:
* verification that the modified files don't contain trailing spaces.
You can use `sed 's/\s*$//' -i "$f"` if you want to clean your files before pushing your PR.
* verification that the style of our C and C++ code is respected using `astyle`
(to the exception of the following folders: `navit/support/`, `navit/fib-1.1/`, `navit/traffic/permanentrestrictions/`).
You can use the following command on the files you are modifying (replacing `$f` by your file name):
`astyle --indent=spaces=4 --style=attach -n --max-code-length=120 -xf -xh "${f}"`
* check for compliance with the DTD using xmllint on the modified files. You can check this locally by using:
`xmllint --noout --dtdvalid navit/navit.dtd "$f"`
* verification that the style of our Java code follows our standards using `./gradlew checkstyleMain`
.. note::
When you submit a PR make sure your branch is up-to-date with the trunk branch to avoid having checks on files you did
not modified.
Coding Style
============
We try to follow those simple rules:
* indentation is done using 4 spaces
* the return type of a function is specified on the same line as the function name
* the open brackets should be at the end of the line (on the same line as the function name or the if/for/while statement)
* out line length is of 120 characters
To help us keeping a coherent indentation, we use astyle on C, C++ and java files. Usage example:
.. code-block:: C
astyle --indent=spaces=4 --style=attach -n --max-code-length=120 -xf -xh my_file.c
.. note::
Because of the bug: [https://sourceforge.net/p/astyle/bugs/230/](https://sourceforge.net/p/astyle/bugs/230/) on astyle,
we cannot rely on astyle to handle properly the line length of 120 characters that we choose.
It would be recommended to set that line length in the editor you are using.
Character encoding and line breaks
----------------------------------
All non-ascii-strings must be utf-8 encoded. Line breaks consist of a linefeed (no carriage return).
C Standard
----------
C95. That means:
* No inline declarations of variables
Instead of
.. code-block:: C
{
do_something();
int a=do_something_else();
}
use
.. code-block:: C
{
int a;
do_something();
a=do_something_else();
}
* No dynamic arrays
Instead of
.. code-block:: C
void myfunc(int count) {
struct mystruct x[count]
}
use
.. code-block:: C
void myfunc(int count) {
struct mystruct *x=g_alloca(count*sizeof(struct mystruct));
}
* No empty initializers
Instead of
.. code-block:: C
struct mystruct m={};
use
.. code-block:: C
struct mystruct m={0,};
* Use `/*` and `*/` for comments instead of `//`
.. note::
The restriction to C95 exists mainly to help the [[WinCE]] port, which uses a compiler without full support for C99. Once all platforms supported by Navit use a compiler capable of C99, this decision may be reconsidered.
Use of libraries
----------------
* Navit uses `GLIB <http://developer.gnome.org/glib/>`_ extensively. In general, code should use GLib's functions in preference to functions from libc.
For example, use `g_new()` / `g_free()` / `g_realloc()`, rather than `malloc()` / `free()` / `realloc()`, `g_strdup()` rather than `strdup()`, `g_strcmp0()` rather than `strcmp()` etc.
* Unfortunately, not all platforms that Navit runs on have a native GLib version.
For these platforms, there is code replacing these libraries under `navit/support/`.
Take care to only use functions from GLib (or other libraries), that is also present under `navit/support/`.
If you need something that is not present there, please discuss it on IRC - it may be possible to add it to the support code.
Comments
--------
General guidelines
``````````````````
* Comments for the entire `file` and `classes/structs/methods/functions` is the `'minimum requirement`'. Examples see below.
* Please comment your code in a significant and reasonable way.
* A quick description of (complicated) algorithms makes it easier for other developers and helps them to save a lot of time.
* Please add a doxygen description for all function you should add. You are we1come to add it too to older functions. Doxygen result can be found `there <http://doxygen.navit-project.org>`_
Example :
.. code-block:: C
/**
* @brief Change the current zoom level, zooming closer to the ground.
*
* This sentence starts the "detailed" description (because this is a new
* paragraph).
*
* @param navit The navit instance
* @param factor The zoom factor, usually 2
* @param p The invariant point (if set to NULL, default to center)
* @returns nothing
*/
void navit_zoom_in(struct navit *this_, int factor, struct point *p)
Templates
`````````
This is an example how you could (should) comment your files and functions. If you have any suggestions for improvement, please feel free to [[Talk:Programming_guidelines|discuss]] them with us. These templates should be doxygen-conform - if not, please correct them. A more comprehensive overview of possible documentation can be found `here <http://www.stack.nl/~dimitri/doxygen/manual.html>`_.
Files
'''''
.. code-block:: C
/** @file can.cpp
* @brief CAN-Camera Framework :: CAN container class and high level functions
*
* Some documentation regarding this file.
*
* @Author Stefan Klumpp <sk@....>
* @date 2008
*/
<include "can.h">
.
.
.
Classes/Structs/Functions/Methods
'''''''''''''''''''''''''''''''''
.. code-block:: C
/**
* @brief A short description of this function
*
* A lot more of documentation regarding this function.
* @param raw_data Some string to pass to the function
* @return Nothing
*/
void CanData::processData(string &raw_data) {
.
.
.
}
Java standards
--------------
For the Java code we follow the Google coding conventions from Google Java Style that can be found at `<https://google.github.io/styleguide/javaguide.html>`_.
This style is enforced by using Checkstyle. Its definition file can be found at the root of the repository:
`checkstyle.xml <https://github.com/navit-gps/navit/blob/trunk/checkstyle.xml>`_
Please add yourself to the list of authors, if you make a significant change.
|
