--===============0703739306==
Content-Type: multipart/signed;
  boundary="nextPart1320583.4oGNXg1I8i";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1320583.4oGNXg1I8i
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello,
In my opinion, exceptions may be used for the cases where there is somethin=
g=20
that does not happen too often, like "someone" deleted the file between I=20
selected it and the application used it. However, I see their main strentch=
=20
in cases, where the code is debuged. Insted of just getting segfault, sigab=
rt=20
or whatever, an exception that contains a text "Invalid input to function=20
SomeFunc in file xx.cpp", causing the program to crash. Yes, the exception =
is=20
left unhandled, however, the programmer instantly knows, what was wrong, he=
=20
doesn't have to hunt it all over the code.

I would quite like to see exceptions in some reasonable amount in the libs.=
=20
Well, in Qt as well, but it does not belong here as much..

=2D-=20

Windows are like..
windows. Shiny but fragile and expensive.

Michal Vaner (Vorner)


--nextPart1320583.4oGNXg1I8i
Content-Type: application/pgp-signature

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

iD8DBQBDqXc07/oWwynB3bIRAnLAAJ4kCH+Sm5M5XojQ7sodH7CX/zADhwCdG9q1
PP7ePPBF/FahdPbkopuT/K4=
=h7yP
-----END PGP SIGNATURE-----

--nextPart1320583.4oGNXg1I8i--


--===============0703739306==
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 <<

--===============0703739306==--