commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25818] - BinaryHeap.remove(Object) seems to break heap order
Date Thu, 01 Jan 2004 18:55:45 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25818>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25818

BinaryHeap.remove(Object) seems to break heap order





------- Additional Comments From phil@steitz.com  2004-01-01 18:55 -------
Thanks, Stephen.  I am completing final testing/review of a fix Modifing
remove() to decide whether to percolate up or down, and adding percolateUp
methods that take start indexes.  All tests (incl the one you just suggested w/
"BinaryHeap" in place of "BinaryBuffer") pass.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message