[Kde-pim] coding style (Re: New Maintainer of KMail)

[Kevin Krammer]

--===============0330386510==
Content-Type: multipart/signed;
  boundary="nextPart1661104.3LDLFC8mMN";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1661104.3LDLFC8mMN
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 05 February 2008, David Faure wrote:

> Huho, a discussion on coding style, we can hear the bikeshed coming...
> I recommend adopting the kdelibs coding style (which is quite close to the
> Qt coding style but a bit more adapted to opensource development), which =
is
> a much better idea than debating over N different coding styles that nobo=
dy
> will ever agree upon. By choosing the kdelibs style you also make it easi=
er
> for kde developers to switch between "coding in kdelibs" and "coding in
> kdepim" (and any other module that adopts the same style).

Isn't there a KDEPIM coding style already?

Searching....

Ah, here it is:
http://pim.kde.org/development/coding.php

Cheers,
Kevin
=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart1661104.3LDLFC8mMN
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHqMBTnKMhG6pzZJIRAs8+AJ92GVTtmdZyHuWlgq+sOpm9r4x+wwCeLcic
DNF5StCRwzCUD4BGuXYRh0U=
=6h21
-----END PGP SIGNATURE-----

--nextPart1661104.3LDLFC8mMN--

--===============0330386510==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
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/
--===============0330386510==--