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

[Frerich Raabe]

On Tuesday 29 April 2003 15:28, Marc Mutz wrote:
> So, to summarize:
>   -no-stl doesn't discourage STL container use, it _en_courages it,
>    b/c a needed STL algorithm not available in the QTL does not work
>    with Qt-no-stl, so you have to change the container class.
>   -stl does not encourage STL container use any more than -no-stl
>    already does; it _en_courages sticking to Qt containers, b/c a needed
>    STL algorithm not in the QTL _does_ work with Qt-stl, so don't have
>    to change the container class.

The only reason I can think of why somebody would want -no-stl is to shave off 
some presumably marginal compile time. CVS log for README.qt-copy didn't 
explain that recommendation either.

- Frerich