Talk:Coding style - Revision history

Gagh: Moved first question to a section, content indexed correctly now

2007-05-27T20:43:38Z

Moved first question to a section, content indexed correctly now

2007-05-26T21:13:35Z

Should namespaces be used

2007-05-21T19:54:06Z

Hungarian notation

2007-05-21T19:51:01Z

CamelCase

2007-05-21T19:43:43Z

More typo's

2007-05-21T19:41:59Z

Fixed a stupid typo

2007-05-21T19:41:06Z

AStyle, should it be on ANSI?

2006-08-31T17:02:14Z

2006-04-08T13:15:36Z

2006-04-01T14:52:03Z

Request for coding standard for comments.

New page

How about comments?

← Older revision		Revision as of 20:43, 27 May 2007
Line 1:		Line 1:
−	How about comments?	+	== How about comments? ==

	Well I'm not an developer. It is pretty safe to say use "//" (C++ style) comments, and not the C style ones.		Well I'm not an developer. It is pretty safe to say use "//" (C++ style) comments, and not the C style ones.

← Older revision		Revision as of 21:13, 26 May 2007
Line 20:		Line 20:

	It is not very clearly stated, but it looks that [http://en.wikipedia.org/wiki/Hungarian_notation Hungarian notation] should be used in the names of variables.		It is not very clearly stated, but it looks that [http://en.wikipedia.org/wiki/Hungarian_notation Hungarian notation] should be used in the names of variables.
		+
		+	== Should namespaces be used ==
		+
		+	What about namespaces?
		+
		+	While implementing a plugin, I started wondering if we should put the plugin in a separate namespace.
		+
		+	As there is nothing specified, I did it anyway, but I think it might be a good idea for C::B to use namespaces.

← Older revision		Revision as of 19:54, 21 May 2007
Line 16:		Line 16:

	Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters.		Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters.
		+
		+	== Hungarian notation ==
		+
		+	It is not very clearly stated, but it looks that [http://en.wikipedia.org/wiki/Hungarian_notation Hungarian notation] should be used in the names of variables.

← Older revision		Revision as of 19:51, 21 May 2007
Line 10:		Line 10:

	Don't know if and how this can be done, but that would be very handy to have.		Don't know if and how this can be done, but that would be very handy to have.
		+
		+	== CamelCase ==
		+
		+	From the article it seems [http://en.wikipedia.org/wiki/CamelCase CamelCase] should be used for all variable and function names.
		+
		+	Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters.

← Older revision		Revision as of 19:43, 21 May 2007
Line 9:		Line 9:
	As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.		As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.

−	Don't know ~~how~~ if and how this can be done, but that would be very handy to have.	+	Don't know if and how this can be done, but that would be very handy to have.

@@ Line 5: / Line 5: @@
 == AStyle, should it be on ANSI? ==
-As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B settings?
+As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B setting?
 As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.
 Don't know how if and how this can be done, but that would be very handy to have.

← Older revision		Revision as of 19:41, 21 May 2007
Line 2:		Line 2:

	Well I'm not an developer. It is pretty safe to say use "//" (C++ style) comments, and not the C style ones.		Well I'm not an developer. It is pretty safe to say use "//" (C++ style) comments, and not the C style ones.
		+
		+	== AStyle, should it be on ANSI? ==
		+
		+	As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B settings?
		+
		+	As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.
		+
		+	Don't know how if and how this can be done, but that would be very handy to have.

← Older revision	Revision as of 17:02, 31 August 2006
(No difference)

← Older revision		Revision as of 13:15, 8 April 2006
Line 1:		Line 1:
	How about comments?		How about comments?
		+
		+	Well I'm not an developer. It is pretty safe to say use "//" (C++ style) comments, and not the C style ones.