--===============1084247638==
Content-Type: multipart/signed;
  boundary="nextPart3329408.k8poIRZtOV";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3329408.k8poIRZtOV
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 07 December 2005 19:05, Volker Lukas wrote:
> Thiago Macieira wrote:
> > [...]
> > So you can expect people to compile it with -fno-exceptions. If you wri=
te
> > applications that rely on exceptions being enabled in Qt, you'll be
> > shooting yourself in the foot. Don't do that.
>
> No. The user who disables it is a fault here. Exception support is needed
> for *correct* programs to be executed *correctly*. If the user willfully
> asks the compiler to produce incorrect output, he has to live with the
> outcome. He can not just assume that nobody uses exceptions in conjunction
> with Qt.

If the application developer wants to deploy on Linux systems _and_ use the=
=20
systems Qt3 installation, he can safely assume it was built without=20
exceptions because of the problems earlier GCC versions had with them and s=
o=20
most (all+) software assumes -fno-exceptions

Might change for Qt4 though.

Cheers,
Kevin
=2D-=20
Kevin Krammer <kevin.krammer@gmx.at>
Qt/KDE Developer, Debian User
Moderator: www.mrunix.de (German), www.qtforum.org

--nextPart3329408.k8poIRZtOV
Content-Type: application/pgp-signature

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

iD8DBQBDlyrTnKMhG6pzZJIRAo1/AJwPGuIpq2mFFm8t7KjuAVShLUXAQQCeN+vl
Tf4jRhlUjk/M9m0Ceq13PII=
=JV/i
-----END PGP SIGNATURE-----

--nextPart3329408.k8poIRZtOV--

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

--===============1084247638==--