On 21.12.08 15:47:18, Robert Hairgrove wrote:
> For a long time, Qt supported a lot of older compilers which had trouble
> with the C++ standard template library. Now that support for these old
> compilers is being phased out, and the STL is mature now and supported
> by all the major vendors, I wonder why there is a need for
> QSharedPointer when there is already a very nice one in the Boost library?
boost is an additional dependency, which some people don't want to have
(especially customers make a difference here). And I'm not sure wether it
builds on all platforms that Qt supports.
> There are a lot of these substitute classes in the Qt library ... QList,
> QByteArray, etc. QString offers a lot more comfort than std::string,
> IMHO, and therefore has added value. But it would be nice if more of the
> STL were incorporated into Qt and not need those "do-it-yourself"
> classes any more (just IMHO :) ).
Not going to happen before Qt5, as any such change would be BiC. And even
then I doubt Qt Software is going to remove QList or QMap, because they
simply provide different semantics than the stl counterparts (apart from
the implicit sharing).
You single-handedly fought your way into this hopeless mess.
Qt-interest mailing list