Hi, On Fri, 2011-09-23 at 12:14 +0800, Andreas Halm wrote: > Hi all, > > Just a quick note of which just occurred to me while implementing the stuff > mentioned below ... > > So as apply(iterator,iterator) is not templated on the iterator type, the > input iterators always have to be vector iterators. So a list wouldn't do in > this case, for example. However, as the child list in a node is not derived > from a vector nor any STL class, you can not even use that function to > iterate over the children of a node, which seems to be its use at least for > the IntersectAction as you describe below. Of course you can always copy the > children to a vector and iterate over that. > > I just would like to understand what that function is for, I see no usage > scenario right now.
it was more for external use and most likely not primarily written with the child field in mind as the assumption was one would start with the parent ;) I'll change the iterators to be templated. > Btw, the implementation of ActionBase::apply(Node*) does look a bit weird to > me, performance-wise. Especially if you consider it might be used much more > often than the iterator version. typically once or twice per frame, so I guess we did not look into it to much, but you're right generating a dummy vector every time does not look to clever on our side ;) kind regards gerrit ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
