Introduce splaytree.KeyNotFoundError and use it for reporting
authorkasperl@chromium.org <kasperl@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 25 Mar 2009 12:14:13 +0000 (12:14 +0000)
committerkasperl@chromium.org <kasperl@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 25 Mar 2009 12:14:13 +0000 (12:14 +0000)
commitfc0af92f6095208bf4fee7e7385478e15b86b0a7
tree033f28bf151f493dbeadb01d79d6228baade2817
parentbd8816efb0a6ba2ef88425f8c414c9775eea6cb6
Introduce splaytree.KeyNotFoundError and use it for reporting
issues when removing non-existing nodes from a SplayTree.
Review URL: http://codereview.chromium.org/42599

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1609 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
tools/splaytree.py
tools/tickprocessor.py