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

[George Staikos]

On Monday 28 April 2003 14:40, Werner Trobin wrote:
> >    We already have std::vector equivalence in Qt.  What you are saying is
>
> that
>
> > only things that cannot be done with Qt may be done with STL?  I will be
> > interested to see this.
>
> Okay, this is the first example that came to my mind :-)
>
> Suppose you have a QValueVector in your FooGadget class and would like to
> call some external library function (e.g. to perform a highly optimized
> assembler FFT of the sequence in your vector), taking a plain vanilla C
> array. You can't just call the method with your QValueVector, as you don't
> have any guarantees concerning the layout of the internal data.
>
> Using a std::vector solves the problem, as std::vector is guraranteed to
> keep the internal data in an array. You just have to pass the pointer to
> the first element in the vector (and probably the size as separate
> parameter) and you're done. Piece of cake.

   So why not implement this in kde-qt-addons or something like that if TT 
can't accept that?  I am fully aware of how STL works:

On Monday 28 April 2003 20:31, George Staikos wrote:
>   Sure... I use STL regularily.  In fact, I've written more STL code than Qt 
> code in the past 2 weeks.


-- 
George Staikos
KDE Developer					http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/