From kde-core-devel Fri May 25 20:46:36 2007 From: Thomas Zander Date: Fri, 25 May 2007 20:46:36 +0000 To: kde-core-devel Subject: Re: Back to kDebug Message-Id: <200705252246.36869.zander () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=118012611319677 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2016610.yhWGsLfznl" --nextPart2016610.yhWGsLfznl Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 25 May 2007 18:50:53 Lubos Lunak wrote: > =A0this should be a follow-up to > http://lists.kde.org/?l=3Dkde-core-devel&m=3D116903044203449&w=3D2 . I'd = like > to do something about it before it gets forgotten even more. On this topic; I was one of the few people in that thread that had some doubts about=20 having it behave more like qDebug. Over the weeks I noted that any and=20 all objections of mine were based on old experience and misconceptions. I=20 now really want to have the 'endl' part be optional and space adding=20 around types be added. So, can't we simply extend qdebug to know about sections? Cheers! =2D-=20 Thomas Zander --nextPart2016610.yhWGsLfznl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBGV0ssCojCW6H2z/QRAvoOAKDPnmICFMdVPakH542sQdzHE7Xl4gCg5/RJ LlTnnwsUs8QCKql2vIg1+I0= =hwQe -----END PGP SIGNATURE----- --nextPart2016610.yhWGsLfznl--