17 Jul
2012
17 Jul
'12
11:26 a.m.
On 17 Jul 2012, David C. Rankin verbalised:
On 07/17/2012 01:01 AM, David C. Rankin wrote:
The advantage of the STL stuff is that it is very very heavily tested,
heavily optimized and someone else fixes bugs in it :)
--
NULL && (void)
private:
/**
* Adds the entries of given the STL to mSources
*/
177 void addSources(const std::list<Source*>& inList);
Since this is a private: member of class Kima : public KPanelApplet, TQToolTip
{, I don't know if the using namespace std; hint was the issue here. What say
the experts?
One more note on this for the project. If we see areas where we can
completely get away from the STL for doing things, I'm all for
recoding to eliminate STL where doable. In all the major gcc
transitions, I always end up fighting STL stuff. Just seems that
custom standard compliant code always come through these type of
changes much better than the STL implementations. Just my uneducated
$.02.