From Christian Ehrlicher, "during profiling my program I found out that there's a lot of memory (de)allocation going on in OverlayNode::cut().
From Christian Ehrlicher, "during profiling my program I found out that there's a lot of memory
(de)allocation going on in OverlayNode::cut().

So instead creating inner-loop variables 'distances' and 'newVertices'
every time, I moved the creation out of the loop and just do a clear() +
reserve() inside the loop. This allows std::vector<> to reuse the old
memory instead allocating new when the new size <= oldsize."


artoolkit/osg,marchelbling/osg,scrawl/osg,openscenegraph/osg,jtorresfabra/osg,marchelbling/osg,jtorresfabra/osg,scrawl/osg,scrawl/osg,openscenegraph/osg,jtorresfabra/osg,tomasthoresen/osg,tomasthoresen/osg,openscenegraph/osg,artoolkit/osg,jtorresfabra/osg,openscenegraph/osg,marchelbling/osg,scrawl/osg,tomasthoresen/osg,tomasthoresen/osg,marchelbling/osg,artoolkit/osg,artoolkit/osg