This is a discussion on assertions in kde plugins - KDE ; --===============0224473955== Content-Type: multipart/signed; boundary="nextPart1665469.PVoB13XD3K"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1665469.PVoB13XD3K Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, can you use Q_ASSERT in a sensible way in a kde plugin? The nice thing abou= t=20 assertions is that they tell you ...
--===============0224473955==
Content-Type: multipart/signed;
boundary="nextPart1665469.PVoB13XD3K";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
--nextPart1665469.PVoB13XD3K
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Hi,
can you use Q_ASSERT in a sensible way in a kde plugin? The nice thing abou=
t=20
assertions is that they tell you where it happened bevore bailing out, but=
=20
kde plugins don't have a stderr to output - or where do I have to look for=
=20
the error message?
Ciao
Uwe
=2D-=20
I knew I'd hate COBOL the moment I saw they'd used "perform" instead of
"do".
-- Larry Wall on a not-so-popular programming language
--nextPart1665469.PVoB13XD3K
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQBD/z31vcDpH3KqcV4RAkFcAKDF2ff0zsfRzG+L6AdhHbJ4XLxMMAC ghSB5
mLRzv2LzWoVgbTgHJbCtpQc=
=HyTE
-----END PGP SIGNATURE-----
--nextPart1665469.PVoB13XD3K--
--===============0224473955==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
--===============0224473955==--
