sites

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs

commit c61d77b4910aa3683d5e534a90a20940ab025de7
parent f3055e6bf1bff0b5c48948f5d4b000fe7b3e90d8
Author: Andrew Antle <andrew.antle@gmail.com>
Date:   Wed, 26 Aug 2009 03:26:35 -0400

Changed 'a guidelines gets handy' to 'guidelines become handy in order'.
Changed 'Due the fact, that most' to 'Due to the fact that most of the'.
Diffstat:
Msuckless.org/common/style_guide.md | 8++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/suckless.org/common/style_guide.md b/suckless.org/common/style_guide.md @@ -3,13 +3,13 @@ Style guide of code hosted on suckless.org When it comes to code style questions, it is very likely that individual programmers will disagree. It is absolutely fine to use an individual style for individual projects, especially if only one developer is involved. However, if -there are two or more programmers involved in a project, a guidelines gets -handy to meet the first basic rule we follow: +there are two or more programmers involved in a project, guidelines become +handy in order to meet the first basic rule we follow: * Code developed by different individuals should follow a common style among those to found a consistent base. Thus consistency in the code style being used is more important than any -particular detail of the style itself. Due the fact, that most software of +particular detail of the style itself. Due to the fact that most of the software of suckless.org has been developed by more than one individual, some sort of common style found in the code appeared during the past years. This common style is described in detail, further on. @@ -40,7 +40,7 @@ in C. However we argue that in general C++ software performs poorer than software written in C, because of its tendency to complexity and its hidden pitfalls like expensive function calls in loops or too many inlines. -All these problems do not happen with C, because C is too simple for being +All these problems do not happen with C, because C is too simple to be misused in our opinion. So the second rule of this style guide concludes: