Re: kdelibs coding style for quanta

--===============0737614124==
Content-Type: multipart/signed;
  boundary="nextPart10279172.YO8pDotcue";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart10279172.YO8pDotcue
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Wednesday 23 September 2009 00:55:21 Niko Sams wrote:
> On Wed, Sep 23, 2009 at 05:52, Matt Rogers <[email protected]> wrote:
> > Hi,
> >
> > Even though there's a decent HACKING file in place for quanta, there's
> > still a bunch of places (even in newer code) where the code doesn't mat=
ch
> > the HACKING file. Are there any objections to switching to the kdelibs
> > coding style?
>=20
> I'm all for it.
> However is it a good idea to switch from 2 spaces to 4 spaces?
>=20
> Niko

=46or me, personally, 2 spaces is not enough indentation to really be that=
=20
readable.=20

More objectively, it's a toss up, since some parts of the code are 2 spaces=
,=20
other newer parts are 4 spaces. If there are no other objections, I was jus=
t=20
going to use 4 spaces, as per the kdelibs coding style guidelines on techba=
se.
=2D-=20
Matt

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEABECAAYFAkq6UesACgkQA6Vv5rghv0eP9ACdGA9ExIV1QJOGhAV+ZWw90ktZ
S7wAoKhCFkFFajmwM/l6wQQy4npfV3dO
=Lo42
-----END PGP SIGNATURE-----

--nextPart10279172.YO8pDotcue--

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

_______________________________________________
quanta-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/quanta-devel

--===============0737614124==--