Projects/KDevelop4/CodingStyle - Revision history

Milianw at 22:08, 11 November 2012

2012-11-11T22:08:51Z

Milianw at 22:00, 11 November 2012

2012-11-11T22:00:11Z

Milianw at 21:57, 11 November 2012

2012-11-11T21:57:03Z

Milianw: Created page with "The current KDevelop code base is very inconsistent when it comes to the coding style. So please adhere to the file's coding style you are working on / patching. For new files /..."

2012-04-19T22:59:27Z

Created page with "The current KDevelop code base is very inconsistent when it comes to the coding style. So please adhere to the file's coding style you are working on / patching. For new files /..."

New page

The current KDevelop code base is very inconsistent when it comes to the coding style. So please adhere to the file's coding style you are working on / patching.

For new files / projects / plugins, please use the [[Policies/Kdelibs_Coding_Style]] guidelines.

@@ Line 2: / Line 2: @@
 For new files / projects / plugins, please use the [[Policies/Kdelibs_Coding_Style]] guidelines. Here are a few special additions:
 == Class Initialization ==
@@ Line 9: / Line 32: @@
 class Foo : public Bar {
 public:
-  Foo(int i, int j) : Bar(i), bla(j) {}
+    Foo(int i, int j) : Bar(i), bla(j) { /* do stuff */ }
 private:
-  int bla;
+    int bla;
 };
@@ Line 18: / Line 41: @@
+{
 public:
-  Foo(int i, int j);
+    Foo(int i, int j);
 private:
-  int m_bla;
+    int m_bla;
 };
 // foo.cpp
@@ Line 27: / Line 50: @@
 , m_bla(j)
+{
+}
 </syntaxhighlight>
@@ Line 32: / Line 56: @@
 == Using Namespaces ==
-Never add a "using namespace ..." to a header. Do use that though in every .cpp file , esp. for the KDevelop namespace.
+Never add a "using namespace ..." to a header. Do use that though in every .cpp file , esp. for the KDevelop namespace. Public API should always be in the KDevelop namespace.

← Older revision		Revision as of 22:00, 11 November 2012
Line 29:		Line 29:
	}		}
	</syntaxhighlight>		</syntaxhighlight>
		+
		+	== Using Namespaces ==
		+
		+	Never add a "using namespace ..." to a header. Do use that though in every .cpp file , esp. for the KDevelop namespace.

← Older revision		Revision as of 21:57, 11 November 2012
Line 1:		Line 1:
	The current KDevelop code base is very inconsistent when it comes to the coding style. So please adhere to the file's coding style you are working on / patching.		The current KDevelop code base is very inconsistent when it comes to the coding style. So please adhere to the file's coding style you are working on / patching.

−	For new files / projects / plugins, please use the [[Policies/Kdelibs_Coding_Style]] guidelines.	+	For new files / projects / plugins, please use the [[Policies/Kdelibs_Coding_Style]] guidelines. Here are a few special additions:
		+
		+	== Class Initialization ==
		+
		+	<syntaxhighlight lang="cpp-qt">
		+	// wrong foo.h
		+	class Foo : public Bar {
		+	public:
		+	Foo(int i, int j) : Bar(i), bla(j) {}
		+	private:
		+	int bla;
		+	};
		+
		+	// correct foo.h
		+	class Foo: public Bar
		+	{
		+	public:
		+	Foo(int i, int j);
		+	private:
		+	int m_bla;
		+	};
		+	// foo.cpp
		+	Foo::Foo(int i, int j)
		+	: Bar(i)
		+	, m_bla(j)
		+	{
		+	}
		+	</syntaxhighlight>