From kde-core-devel Thu Jul 20 18:26:55 2006 From: "Aaron J. Seigo" Date: Thu, 20 Jul 2006 18:26:55 +0000 To: kde-core-devel Subject: Re: kdelibs coding style Message-Id: <200607201226.55332.aseigo () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=115342128617661 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2113515.q9fZJ9XMjP" --nextPart2113515.q9fZJ9XMjP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 20 July 2006 10:05, Adam Treat wrote: > However, applying this rule in patches for newly modified code is going to > make the situation worse. The style will differ from method to method for > a very long time. I doubt every method will be touched in time for KDE4 > release. style already differs from method to method ... often within the same metho= d!=20 so it's not like we're going to be making a mess, it already is one ;) that said ... i did this same thing with kicker over the last (nearly) 2=20 years .. and it has resulted in noticeable improvements. granted i touched = a=20 lot more of kicker than we may touch in kdelibs in 2 years time, but it doe= s=20 seem to work as a way to fix things without ruining revision history. =2D-=20 Aaron J. Seigo Undulate Your Wantonness GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 =46ull time KDE developer sponsored by Trolltech (http://www.trolltech.com) --nextPart2113515.q9fZJ9XMjP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBEv8rv1rcusafx20MRAuYJAJ9ESYK0/V1VQD7kOW7y1zXQGMW6YwCfdvXw CzMZNNDJ0awvA++e9i3frI0= =sMHe -----END PGP SIGNATURE----- --nextPart2113515.q9fZJ9XMjP--