[Kde-pim] coding-style for KDEPIM

[guy-kde]

Am 07.03.2013 16:26, schrieb Allen Winter:
> On Thursday 07 March 2013 11:26:43 AM Guy Maurel wrote:
>> As discussed at the KDEPIM meeting, Berlin, 3 March 2013, all the 
>> files of
>> KDEPIM will be reviewed to follow the coding style. This will be done 
>> over a
>> long time, directory after directory, for each of the rules.
>> 
>> I opened a new URL for that:
>>    http://techbase.kde.org/Policies/Kdepim_Coding_Style
>> 
>> This is still in construction.
>> Please, have a look to my proposal and comment it.
>> Any suggestions, fixes are welcome.
>> 
> Guy,
> We already have a coding style page at
> http://community.kde.org/KDE_PIM/Development/CodingStyle/Korganizer
it is fine...

> So you can copy that in and make changes as needed.
> Then remove it.
Ineed some more time...

> I do object to the 4 space indent level. I like 2 better.
I know!
This is a question, we will never found the best answer.
One answer could be "it is parameter one can/may set to 2 or 4"
Let's try it...

> especially if we keep to a 100-char line length limit.
100 or 120, it doesn't matter.
I have already seen some expressions with only 2 operants, which
are longer.
This could be better a "warning" for the developerto have a better
look of the line, and make (maybe) some modification itself.

> I need to change Krazy checker accordingly.
krazy cannot solve all the rules, ie.
my_type* my_variable;
or
my_type *my_variable;

The second one is recomanded, but only a compiler could find it.

> Why can't we do one big astyle change all in one go?
YES. For the first approach and *now*.

My goal is to use a compiler (clang) and include some "plugins" with 
the rules we wanted to have.
-- 
guy-kde
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/