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

[Daniel Stone]

On Tue, Apr 29, 2003 at 10:38:00AM +0200, Alexander Kellett wrote:
> On Tue, Apr 29, 2003 at 10:24:41AM +0200, Stephan Kulow wrote:
> > OK. Fine. If you don't like STL, don't use it. But why do you want to prevent
> > others from using it together with Qt?
> 
> 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.

If someone orphans their code and you pick it up, do whatever the hell
you like with it. But until they do, it's their pissing patch. They pick
the coding style, function naming, class naming, all that sort of stuff.
And it's their decision, their discretion.

-- 
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/d795ca6d/attachment.sig>