Update 'Coding Style'
parent
aa8f589a8a
commit
c2bdbdcb47
1 changed files with 3 additions and 3 deletions
|
@ -29,11 +29,11 @@ This document discusses practices and style for programmers working on the BigWh
|
|||
Above all, the following rule from the GNOME developer documentation should always be followed.
|
||||
>The single most important rule when writing code is this: check the surrounding code and try to imitate it.
|
||||
>
|
||||
>As a maintainer it is dismaying to receive a patch that is obviously in a different coding style to the surrounding code. This is >disrespectful, like someone tromping into a spotlessly-clean house with muddy shoes.
|
||||
>As a maintainer it is dismaying to receive a patch that is obviously in a different coding style to the surrounding code. This is disrespectful, like someone tromping into a spotlessly-clean house with muddy shoes.
|
||||
>
|
||||
>So, whatever this document recommends, if there is already written code and you are contributing to it, keep its current style >consistent even if it is not your favorite style.
|
||||
>So, whatever this document recommends, if there is already written code and you are contributing to it, keep its current style consistent even if it is not your favorite style.
|
||||
>
|
||||
>Most importantly, do not make your first contribution to a project a change in the coding style to suit your taste. That is >incredibly disrespectful.
|
||||
>Most importantly, do not make your first contribution to a project a change in the coding style to suit your taste. That is incredibly disrespectful.
|
||||
|
||||
## Formatting
|
||||
### Indentation
|
||||
|
|
Loading…
Reference in a new issue