[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kdelibs coding style
From:       David Faure <faure () kde ! org>
Date:       2006-08-23 21:06:21
Message-ID: 200608232306.22244.faure () kde ! org
[Download RAW message or body]

On Wednesday 23 August 2006 16:47, Lubos Lunak wrote:
>  So we're going to have a guide that's pretty strict even about things like 
> placement of spaces but not actually require it? 
That would be my idea, yes. A "best practice" or "recommendation".
Just like many things about kdelibs, like putting the variables into the d pointer,
or writing API docs ;)

We still do this for fun, so let's not make it a work environment where you
only get a patch in if it follows 500 rules, with the need for 20 revisions of 
the patch until it actually follows them all.

> How about we then make a  
> list of really required things[*] and call the rest just "recommendations" or 
> whatever, because that's what it's going to be anyway? (Do I have to say that 
> I told you?)
> 
> [*]
> - Indent by 4 spaces, no tabs
Would be a good first step.

> - Try to make it readable, use common sense, 
Those two things are too vague to be of any use in a list of required things :)
Everyone interprets that differently in the end.

> follow the style of the file
Was already the requirement/recommendation, yes.

> > Well, I think we can wrap this up now - editor-specific config-files have
> > been added to kdelibs (like .emacs-dirvars), all we need is to add the
> > kdelibs-coding-style to some webpage, I guess on developer.kde.org...
Hmm the real question is whether to remove the "( foo )" space insertion from kde-emacs :)

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
[prev in list] [next in list] [prev in thread] [next in thread]