Fwd: kdelibs coding style

[Matt Rogers]

On Saturday 22 July 2006 14:32, Andras Mantia wrote:
> On Saturday 22 July 2006 22:15, Matt Rogers wrote:
> > On Saturday 22 July 2006 13:41, Andras Mantia wrote:
> > > On Saturday 22 July 2006 18:08, Alexander Dymo wrote:
> > > > There was a nice discussion on k-c-d about having the same coding
> > > > style in all kdelibs. So let me start another "warm" topic here
> > > > and ask if we want to adapt this policy for KDevelop too? Maybe
> > > > not for the whole KDevelop but for what will constitute
> > > > KDevPlatform in the future?
> > >
> > > Even there I would suggest to apply only for the lib part, not for
> > > the platform plugins.
> > > BTW, I have no problem with the style aside of the curly braces
> > > thing, but I can live with that.
> > >
> > > Andras
> >
> > Please take a look at the coding guidelines on the wiki and see if
> > they meet with your approval, since that's what nearly all of the new
> > code in KDevelop 4 is using.
>
> My coding style is different [*], but I accept what was written there,
> if - as the document says - the files contains the corresponding editor
> modelines.
>
> [*] Main differences: indent with 2 spaces, indent the "case" lines in a
> switch.

Most do. Style is otherwise enforced by the .kateconfig file in the toplevel 
kdevelop directory
--
Matt