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

[Marc Mutz]

On Tuesday 29 April 2003 10:38, Alexander Kellett wrote:
<snip>
> for the reaoson that George has already stated more than just
> a few times. people don't stick around, and inevitably in the
> end people who wish to fix bugs in the code are going to have
> a much more difficult job if its in write-only stl than if its
> in pure qt.
<snip>

OK, so you don't understand STL code. You won't understand QTL code, 
too.

The STL line

result.erase( std::unique(result.begin(), result.end()), result.end() );

would read in QTL:

result.erase( qUnique(result.begin(), result.end()), result.end() );

Wow!
And do you really mean that

result.erase( std::unique( result.begin(), result.end() ),result.end());

is "much more difficult" to maintain or understand than

QStringList::iterator it = result.begin();
for (QStringList::iterator ot = it++; it != result.end(); ot = it++)
    if (*ot == *it) result.remove(ot);

? Wow again!

Marc

-- 
Eternal vigilance is the price of liberty   -- Thomas Jefferson
-------------- 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/784eacaf/attachment.sig>