Policies/Kdelibs Coding Style/en - Revision history

FuzzyBot: Updating to match new version of source page

2013-05-30T10:31:23Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2013-04-07T18:22:46Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2012-12-08T16:50:56Z

Updating to match new version of source page

Tampakrap: Updating to match new version of source page

2012-01-23T14:53:59Z

Updating to match new version of source page

Tampakrap: Updating to match new version of source page

2011-12-22T19:59:10Z

Updating to match new version of source page

Tampakrap: Updating to match new version of source page

2011-08-23T11:40:47Z

Updating to match new version of source page

Tampakrap: Updating to match new version of source page

2011-07-05T13:18:04Z

Updating to match new version of source page

New page

This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.

'''In short: Kdelibs coding style follows the Qt 4 coding style.'''

== Indentation ==
* No tabs
* 4 Spaces instead of one tab

== Variable declaration ==
* Each variable declaration on a new line
* Each new word in a variable name starts with a capital letter (so-called camelCase)
* Avoid abbreviations
* Take useful names. No short names, except:
** Single character variable names can denote counters and temporary variables whose purpose is obvious
** Variables and functions start with a lowercase letter

Example:
<syntaxhighlight lang="cpp-qt">
// wrong
KProgressBar *prbar;
QString prtxt, errstr;

// correct
KProgressBar *downloadProgressBar;
QString progressText;
QString errorString;
</syntaxhighlight>

== Whitespace ==
* Use blank lines to group statements
* Use only one empty line
* Use one space after each keyword
* For pointers or references, use a single space before '*' or '&', but not after
* No space after a cast

Example:
<syntaxhighlight lang="cpp-qt">
// wrong
QString* myString;
if(true){
}

// correct
QString *myString;
if (true) {
}
</syntaxhighlight>

== Braces ==
As a base rule, the left curly brace goes on the same line as the start of the statement.

Example:
<syntaxhighlight lang="cpp-qt">
// wrong
if (true)
{
}

// correct
if (true) {
}
</syntaxhighlight>

Exception: Function implementations, class, struct and namespace declarations always have the opening brace on the start of a line.

Example:
<syntaxhighlight lang="cpp-qt">
void debug(int i)
{
qDebug("foo: %i", i);
}

class Debug
{
};
</syntaxhighlight>

Use curly braces even when the body of a conditional statement contains only one line.

Example:
<syntaxhighlight lang="cpp-qt">
// wrong
if (true)
return true;

for (int i = 0; i < 10; ++i)
qDebug("%i", i);

// correct
if (true) {
return true;
}

for (int i = 0; i < 10; ++i) {
qDebug("%i", i);
}
</syntaxhighlight>

== Switch statements ==
Case labels are on the same column as the switch

Example:
<syntaxhighlight lang="cpp-qt">
switch (myEnum) {
case Value1:
doSomething();
break;
case Value2:
doSomethingElse();
// fall through
default:
defaultHandling();
break;
}
</syntaxhighlight>

== Line breaks ==
Try to keep lines shorter than 100 characters, inserting line breaks as necessary.

== Qt Includes ==
* If you add #includes for Qt classes, use both the module and class name. This allows library code to be used by applications without excessive compiler include paths.

Example:
<syntaxhighlight lang="cpp-qt">
// wrong
#include <QString>

// correct
#include <QtCore/QString>
</syntaxhighlight>

== Artistic Style (astyle) automatic code formatting ==
You can use [http://astyle.sourceforge.net/ astyle] (>=1.23) to format code or to test if you have followed this document. Run the following command:
<syntaxhighlight lang="text">
astyle --indent=spaces=4 --brackets=linux \
--indent-labels --pad-oper --unpad-paren \
--one-line=keep-statements --convert-tabs \
--indent-preprocessor \
`find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`
</syntaxhighlight>

With astyle (>=2.01) you need to run the following command:
<syntaxhighlight lang="text">
astyle --indent=spaces=4 --brackets=linux \
--indent-labels --pad-oper --unpad-paren \
--keep-one-line-statements --convert-tabs \
--indent-preprocessor \
`find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`
</syntaxhighlight>

A related shell script could be found for unix in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs kdesdk/scripts/astyle-kdelibs] and for windows in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs.bat kdesdk/scripts/astyle-kdelibs.bat].

== Emacs and Vim scripts ==
The "scripts" directory in the kdesdk module contains, among other useful things, some useful additions to the Emacs and Vim text editors that make it easier to edit KDE code with them.

=== Emacs ===
The [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-emacs kde-emacs] directory contains a set of key bindings, macros and general useful code. It is compatible with both GNU Emacs and XEmacs.

To start using kde-emacs, add the following to your .emacs:

<syntaxhighlight lang="text">
(add-to-list 'load-path "/path/to/kde-emacs")
(require 'kde-emacs)
</syntaxhighlight>

Many settings can be changed by editing the "kde-emacs" group via <tt>M-x customize-group</tt>.

For more information, including what the key bindings are and what additional settings you could add to your .emacs, please check <tt>kde-emacs.el</tt> itself.

=== Vim ===
You can find a vim script in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim kdesdk/scripts/kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.

To use the script, include it in your {{path|~/.vimrc}} like this:
<syntaxhighlight lang="text">
source /path/to/kde/sources/kdesdk/scripts/kde-devel-vim.vim
</syntaxhighlight>

Document started by Urs Wolfer. Some parts of this document have been adopted from the Qt Coding Style document posted by Zack Rusin on kde-core-devel.

[[Category:Policies]] [[Category:C++]]

@@ Line 2: / Line 2: @@
 This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.
-'''In short: Kdelibs coding style follows the [http://wiki.qt-project.org/Coding_Style Qt 4 coding style].'''
+'''In short: Kdelibs coding style follows the [http://wiki.qt-project.org/Coding_Style Qt 4 coding style], with one main difference: using curly braces even when the body of a conditional statement contains only one line.'''
 == Indentation ==

← Older revision		Revision as of 11:40, 23 August 2011
Line 1:		Line 1:
		+	<languages />
	This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.		This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.

@@ Line 151: / Line 151: @@
 </syntaxhighlight>
-A related shell script could be found for unix in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs kdesdk/scripts/astyle-kdelibs] and for windows in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/astyle-kdelibs.bat kdesdk/scripts/astyle-kdelibs.bat].
+You can find a shell script to run this command in:
 == Emacs and Vim scripts ==
-The "scripts" directory in the kdesdk module contains, among other useful things, some useful additions to the Emacs and Vim text editors that make it easier to edit KDE code with them.
+The [https://projects.kde.org/projects/kde/kdesdk/kde-dev-scripts/repository/revisions/master/show kde-dev-scripts] directory in the kdesdk module contains, among other useful things, some useful additions to the Emacs and Vim text editors that make it easier to edit KDE code with them.
 === Emacs ===
-The [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-emacs kde-emacs] directory contains a set of key bindings, macros and general useful code. It is compatible with both GNU Emacs and XEmacs.
+The [https://projects.kde.org/projects/kde/kdesdk/kde-dev-scripts/repository/revisions/master/show/kde-emacs kde-emacs] directory contains a set of key bindings, macros and general useful code. It is compatible with both GNU Emacs and XEmacs.
 To start using kde-emacs, add the following to your .emacs:
@@ Line 171: / Line 174: @@
 === Vim ===
-You can find a vim script in [http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim kdesdk/scripts/kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.
+You can find a vim script in [https://projects.kde.org/projects/kde/kdesdk/kde-dev-scripts/repository/revisions/master/raw/kde-devel-vim.vim kde-devel-vim.vim] that helps you to keep the coding style correct. In addition to defaulting to the kdelibs coding style it will automatically use the correct style for Solid and kdepim code. If you want to add rules for other projects feel free to add them in the SetCodingStyle function.
 To use the script, include it in your {{path|~/.vimrc}} like this:

@@ Line 14: / Line 14: @@
 * Take useful names. No short names, except:
 ** Single character variable names can denote counters and temporary variables whose purpose is obvious
-** Variables and functions start with a lowercase letter
+* Variables and functions start with a lowercase letter
 Example:
@@ Line 27: / Line 27: @@
 QString errorString;
 </syntaxhighlight>
 == Whitespace ==

@@ Line 2: / Line 2: @@
 This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formatting of the source code files it is recommended to make use of it.
-'''In short: Kdelibs coding style follows the Qt 4 coding style.'''
+'''In short: Kdelibs coding style follows the [http://wiki.qt-project.org/Coding_Style Qt 4 coding style].'''
 == Indentation ==
@@ Line 138: / Line 138: @@
         --one-line=keep-statements --convert-tabs \
         --indent-preprocessor \
-        `find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`
+        `find -type f -name '*.cpp'-or -name '*.cc' -or -name '*.h'`
 </syntaxhighlight>
@@ Line 147: / Line 147: @@
         --keep-one-line-statements --convert-tabs \
         --indent-preprocessor \
-        `find -type f -name '*.cpp'` `find -type f -name '*.cc'` `find -type f -name '*.h'`
+        `find -type f -name '*.cpp' -or -name '*.cc' -or -name '*.h'`
 </syntaxhighlight>

@@ Line 135: / Line 135: @@
 <syntaxhighlight lang="text">
 astyle --indent=spaces=4 --brackets=linux \
-        --indent-labels --pad-oper --unpad-paren \
+        --indent-labels --pad=oper --unpad=paren \
         --one-line=keep-statements --convert-tabs \
         --indent-preprocessor \
@@ Line 144: / Line 144: @@
 <syntaxhighlight lang="text">
 astyle --indent=spaces=4 --brackets=linux \
-        --indent-labels --pad-oper --unpad-paren \
+        --indent-labels --pad-oper --unpad-paren --pad-header \
         --keep-one-line-statements --convert-tabs \
         --indent-preprocessor \