Closed GoogleCodeExporter closed 9 years ago
These resets don't appear to be necessary. Here's a patch that removes them.
This shaves off about 20% overhead.
A quick scan of all the examples seems to indicate that this breaks nothing.
Original comment by peter....@solide-ict.nl
on 15 Jun 2011 at 3:30
Attachments:
Turns out it does break something.. will work on a better patch
Original comment by peter....@solide-ict.nl
on 16 Jun 2011 at 8:22
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
Keep in mind though that sometimes even the constructor does use the reset
function as well as the reset() is public. So you can even use it in external
code.
Original comment by michiele...@gmail.com
on 16 Jun 2011 at 8:45
Keep in mind though that sometimes even the constructor does use the reset
function as well as the reset() is public. So you can even use it in external
code.
Original comment by michiele...@gmail.com
on 16 Jun 2011 at 8:45
I'm giving up for now, it's a bit too tangled to figure out how to improve this
Original comment by peter....@solide-ict.nl
on 16 Jun 2011 at 9:20
Note that the original request was implemented; get_children caches the
framelist and returns the previously made object when it's still there.
Original comment by peter....@solide-ict.nl
on 16 Jun 2011 at 9:21
@peter thanks for the update, we'll take a closer look at that functionality to
see if any additional enhancements can be made.
Original comment by eclecticgeek
on 16 Jun 2011 at 3:05
A cache for the get_children methods was added in r374. The get_subtree subtree
method is never used.
Original comment by fabien.menager
on 23 Oct 2011 at 2:56
Original comment by eclecticgeek
on 30 May 2013 at 5:15
Original issue reported on code.google.com by
michiele...@gmail.com
on 5 Oct 2009 at 12:41