Reason for -no-stl in qt-copy configure recommendation?

[Daniel Stone]

On Mon, Apr 28, 2003 at 06:27:59PM -0400, George Staikos wrote:
> On Monday 28 April 2003 14:48, Andr? W?bbeking wrote:
> > On Monday 28 April 2003 20:31, George Staikos wrote:
> > >    We are not preventing interoperability.  it is a question of
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > whether KDE CVS, "KDE as a project", should be writing STL code in
> > > KDE CVS.  We have standardized on Qt, not glib, not STL.

Yes, but we use ... let's see.

libart?
glib (was the decision made to pull it in to kdesupport?)
and quite a few other *EXTERNAL* libs.

Just because Qt has been chosen, doesn't mean it's been done to the
detriment of other libraries.

> > and on C++ and STL is part of C++ for many years.
> 
>   So are exceptions, gets(), printf(), and more.  We don't use them (well we 
> try to avoid exceptions whenever possible).

He rebuffed your argument reasonably well, IMO.

-- 
Daniel Stone 	     <daniel at raging.dropbear.id.au>             <dstone at kde.org>
KDE: Konquering a desktop near you - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20030429/fab7a58f/attachment.sig>