Kevin Krammer wrote:
> [...]
> If the application developer wants to deploy on Linux systems _and_ use
> the systems Qt3 installation, he can safely assume it was built without
> exceptions [...]

This is in some way a chicken and egg problem: Programmers fear that Qt is
built with -fno-exceptions, which puts them of from using exceptions. In
consequence, the people building Qt packages are less compelled to give up
this practice. This alone does not say much about whether it is a good or a
bad practice.

> [...] because of the problems earlier GCC versions had with them and
> so most (all+) software assumes -fno-exceptions

I use an older release series myself (3.3.x) and exception support creates
much less problems than support for some other C++ features.

This release series is binary compatible to GCC 3.2, if I recall correctly.
GCC 3.2 has been released in August 2002. This means users of GCC releases
from that time on can easily upgrade their release to an "unproblematic"
version. The intermediary releases 3.0.0 - 3.1.1 were not adopted widely.
So the preceding release series was GCC 2.95, with the first release in
July 1999 (last March 2001). This means that the "problematic" compiler is
basically 6 years old. I do not think that it is reasonable to hold
progress back, just to cater for such an old compiler.

> Might change for Qt4 though.

I hope so.

>> Visit to unsubscribe <<