Talk:Policies/Kdelibs Coding Style: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
::: indeed i did, as that was what was discussed and agreed upon in trysil. given that a majority of the active kdelibs developers were there, including probably our most central ones, i think that's good enough =) --[[User:Aseigo|Aseigo]] 23:01, 16 February 2007 (CET) | ::: indeed i did, as that was what was discussed and agreed upon in trysil. given that a majority of the active kdelibs developers were there, including probably our most central ones, i think that's good enough =) --[[User:Aseigo|Aseigo]] 23:01, 16 February 2007 (CET) | ||
Where it says "Kdelibs coding style follows the Qt 4 coding style." There should be maybe a link that points out Qt 4 coding style. --[[User:Pkpatel88|Pkpatel88]] 23:59, 06 February (CST) | |||
Latest revision as of 06:01, 7 February 2009
The document says: "Use curly braces when the body of a conditional statement contains more than one line, and also if a single line statement is somewhat complex."
I thought we decided that we always want curly braces, no? --Mkretz 21:19, 15 February 2007 (CET)
- my pov: According to Zack's attachement this is not the case. As it makes sense to stick to the Qt style for the libs I'd say the current rule is fine. The attachemet also had the final rule Feel free to break a rule if it makes your code look bad. We should include it as well :) I did not and will not read the whole thread again ;) --Dhaumann 23:30, 15 February 2007 (CET)
- meanwhile aaron already changed it, wheee ;) --Dhaumann
- indeed i did, as that was what was discussed and agreed upon in trysil. given that a majority of the active kdelibs developers were there, including probably our most central ones, i think that's good enough =) --Aseigo 23:01, 16 February 2007 (CET)
Where it says "Kdelibs coding style follows the Qt 4 coding style." There should be maybe a link that points out Qt 4 coding style. --Pkpatel88 23:59, 06 February (CST)