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

[Marc Mutz]

On Tuesday 29 April 2003 12:15, Antonio Larrosa Jiménez wrote:
<snip>
> Yep, I see. But the only difference is that STL has a unique
> algorithm. Nobody prevents anyone to implement that in the next Qt
> version or in kdecore (kde-qt-addon, whatever), and that way we would
> have a unique (how ironic :) ) naming scheme and homogeneous API,
> instead of a fragmented one.
<snip>

How much difference is there in std::unique() vs. qUnique?

And what if someone needs for_each, find_if, accumulate, generate, 
sort(...,...,greater<...>)? Do you volunteer to _re_implement them for 
the QTL, too?

Marc

-- 
Nie wird so viel gelogen wie vor der Wahl, während des Kriegs und nach
der Jagd                                          -- Otto von Bismarck
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20030429/c7d7143a/attachment.sig>