https://wiki.codeblocks.org/api.php?action=feedcontributions&feedformat=atom&user=Gagh 2026-05-06T21:41:27Z User contributions MediaWiki 1.35.0 https://wiki.codeblocks.org/index.php?title=Talk:Coding_style&diff=4682 2007-05-27T20:43:38Z

<p>Gagh: Moved first question to a section, content indexed correctly now</p> <hr /> <div>== How about comments? ==<br /> <br /> Well I'm not an developer. It is pretty safe to say use &quot;//&quot; (C++ style) comments, and not the C style ones.<br /> <br /> == AStyle, should it be on ANSI? ==<br /> <br /> As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B setting?<br /> <br /> As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.<br /> <br /> Don't know if and how this can be done, but that would be very handy to have.<br /> <br /> == CamelCase ==<br /> <br /> From the article it seems [http://en.wikipedia.org/wiki/CamelCase CamelCase] should be used for all variable and function names.<br /> <br /> Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters.<br /> <br /> == Hungarian notation ==<br /> <br /> 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.<br /> <br /> == Should namespaces be used ==<br /> <br /> What about namespaces?<br /> <br /> While implementing a plugin, I started wondering if we should put the plugin in a separate namespace.<br /> <br /> As there is nothing specified, I did it anyway, but I think it might be a good idea for C::B to use namespaces.</div>

Gagh https://wiki.codeblocks.org/index.php?title=Talk:Coding_style&diff=4680 2007-05-26T21:13:35Z

<p>Gagh: Should namespaces be used</p> <hr /> <div>How about comments?<br /> <br /> Well I'm not an developer. It is pretty safe to say use &quot;//&quot; (C++ style) comments, and not the C style ones.<br /> <br /> == AStyle, should it be on ANSI? ==<br /> <br /> As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B setting?<br /> <br /> As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.<br /> <br /> Don't know if and how this can be done, but that would be very handy to have.<br /> <br /> == CamelCase ==<br /> <br /> From the article it seems [http://en.wikipedia.org/wiki/CamelCase CamelCase] should be used for all variable and function names.<br /> <br /> Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters.<br /> <br /> == Hungarian notation ==<br /> <br /> 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.<br /> <br /> == Should namespaces be used ==<br /> <br /> What about namespaces?<br /> <br /> While implementing a plugin, I started wondering if we should put the plugin in a separate namespace.<br /> <br /> As there is nothing specified, I did it anyway, but I think it might be a good idea for C::B to use namespaces.</div>

Gagh https://wiki.codeblocks.org/index.php?title=User:Gagh&diff=4670 2007-05-21T20:16:23Z

<p>Gagh: Moved text from main page that I made by mistake</p> <hr /> <div>= Just a short note about me =<br /> <br /> I'm a professional programmer who can't stop when he gets home. I've been working in different IT jobs over the last 10 years, mostly in industrial and off shore automation.<br /> <br /> When I code at home it is mostly little tools for my own use, but sometimes I help with a few minor tweaks or some testing for programs I use. Having stumbled on C::B, it seems like there is something I can help with and I can also enjoy.<br /> <br /> If there is need somewhere within the project, just drop me a note. At the moment I'm still learning about C::B and am looking at the current thread on the forum about version control. Might jump in and help out in that department, as it is a rather important to have a good version control interface if you want to work on projects with a lot of people.<br /> <br /> I'm also busy writing a client for [http://www.musicpd.org musicpd], as I use it to play my music and there are no nice clients on the MSW platform for it. I just started the client, but have decided to ditch my old IDE and compiler. So I started porting it to C::B and wxWidgets and I might even try to build it on a freebsd box, just for fun.</div>

Gagh https://wiki.codeblocks.org/index.php?title=Talk:Coding_style&diff=4668 2007-05-21T19:54:06Z

<p>Gagh: Hungarian notation</p> <hr /> <div>How about comments?<br /> <br /> Well I'm not an developer. It is pretty safe to say use &quot;//&quot; (C++ style) comments, and not the C style ones.<br /> <br /> == AStyle, should it be on ANSI? ==<br /> <br /> As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B setting?<br /> <br /> As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.<br /> <br /> Don't know if and how this can be done, but that would be very handy to have.<br /> <br /> == CamelCase ==<br /> <br /> From the article it seems [http://en.wikipedia.org/wiki/CamelCase CamelCase] should be used for all variable and function names.<br /> <br /> Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters.<br /> <br /> == Hungarian notation ==<br /> <br /> 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.</div>

Gagh https://wiki.codeblocks.org/index.php?title=Talk:Coding_style&diff=4667 2007-05-21T19:51:01Z

<p>Gagh: CamelCase</p> <hr /> <div>How about comments?<br /> <br /> Well I'm not an developer. It is pretty safe to say use &quot;//&quot; (C++ style) comments, and not the C style ones.<br /> <br /> == AStyle, should it be on ANSI? ==<br /> <br /> As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B setting?<br /> <br /> As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.<br /> <br /> Don't know if and how this can be done, but that would be very handy to have.<br /> <br /> == CamelCase ==<br /> <br /> From the article it seems [http://en.wikipedia.org/wiki/CamelCase CamelCase] should be used for all variable and function names.<br /> <br /> Don't know if there should be something more specified like UpperCamelCase for functions and member variables, lowerCamelCase for other variables and function parameters.</div>

Gagh https://wiki.codeblocks.org/index.php?title=Talk:Coding_style&diff=4666 2007-05-21T19:43:43Z

<p>Gagh: More typo's</p> <hr /> <div>How about comments?<br /> <br /> Well I'm not an developer. It is pretty safe to say use &quot;//&quot; (C++ style) comments, and not the C style ones.<br /> <br /> == AStyle, should it be on ANSI? ==<br /> <br /> As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B setting?<br /> <br /> As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.<br /> <br /> Don't know if and how this can be done, but that would be very handy to have.</div>

Gagh https://wiki.codeblocks.org/index.php?title=Talk:Coding_style&diff=4665 2007-05-21T19:41:59Z

<p>Gagh: Fixed a stupid typo</p> <hr /> <div>How about comments?<br /> <br /> Well I'm not an developer. It is pretty safe to say use &quot;//&quot; (C++ style) comments, and not the C style ones.<br /> <br /> == AStyle, should it be on ANSI? ==<br /> <br /> As the AStyle plugin keeps changing the code, shouldn't AStyle have a specific C::B setting?<br /> <br /> As ANSI is given as the standard, it would be nice to have a specific ANSI version for C::B development and plugin development.<br /> <br /> Don't know how if and how this can be done, but that would be very handy to have.</div>

Gagh https://wiki.codeblocks.org/index.php?title=Talk:Coding_style&diff=4664 2007-05-21T19:41:06Z

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

Gagh https://wiki.codeblocks.org/index.php?title=User:Gagh&diff=4663 2007-05-19T01:17:33Z

<p>Gagh: Initial blurp</p> <hr /> <div>Switching to Code::Blocks from emacs on FreeBSD and VS 6 on XP.<br /> <br /> Porting a application I'm working on from VS 6 to GCC and wxWidgets.<br /> <br /> Will notify my progress here and might also do some other work if I get the hang of CB.</div>

Gagh