DRAFT document on coding conventions in kde libraries

[Aaron J. Seigo]

On Sunday 05 March 2006 09:20, Matt Rogers wrote:
>  Nested classes called Private should be removed, IMHO. I think it's ok to
> use them, but we should try to avoid things that are mostly a matter of
> personal preference or style.

meh. it's easy enough to do, appears in very few places (2 times in the 
header, one after the other; a couple times in the source file) and really 
does standardize our use of the PIMPL idiom.

in fact, i'd say unless there was good reason NOT to standardize this we 
should.

note the reasoning against slotFoo given by david, or the common-sense 
avoidance flamewars by trying to dictate {} usage as good examples of things 
we shouldn't standardize ;)

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060306/2dfb3bd1/attachment.sig>