| 3 | | Any source contribution to HelenOS must follow the C style rules described below. This list is, by definition, incomplete. Even if you comply with all the below rules does not mean nobody will comment on your C style. Do try to emulate the style of existing/surrounding code. |
| | 3 | The purpose of having a common coding style is to have a common language. The more consistent the coding style is, the easier it is for others to read your code. |
| | 4 | |
| | 5 | Any source contribution to HelenOS must follow the C style rules described below. Even if you are working on a school assignment, we kindly ask you follow our coding style up front. It's a colossal waste of our resources having to update the coding style in order to merge your changes to our mainline. |
| | 6 | |
| | 7 | This list is, by definition, incomplete. Even if you comply with all the below rules does not mean nobody will comment on your C style. Do try to emulate the style of existing/surrounding code. |
