QT container classes aren't necessarily a missfeature but they're certainly redundant to STL classes. What really is bad though is that the QT container classes we do use are heavily missused. Most notoriously the class QValueList is frequently missused as set class. When this is done, there is a ton of other extremely slow, buggy code that enforces the set property on the list...
We can do much better by converting everything to the most appropriate STL class (which might be completely different from the current QT container!) and exploiting the standard algorithm packages to exploit the exceptionally good code there. I've done some of these conversions in the past, in the most egregious cases, I just did a few more. Here are some tips: >>> Work on private variables first. >>> work on classes low in the inheritance heirarchy. -- New president: Here we go again... Chemistry.com: A total rip-off. Powers are not rights. ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Ktechlab-devel mailing list Ktechlab-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
