Dalibor Topic wrote:
For debugging, yes. For efficiency, no. Creating an ImmutableNode would require reworking the entire TreeMap class to use method calls, rather than field assignments, for manipulating nodes. Adding polymorphic calls is an additional layer of indirection, and will make the overall implementation slower.Since nil is supposed to have children that are also
nil it appears
that at some point nil.right was assiged a value.would it be possible to make nil an "ImmutableNode", so that such assignments are caught and greeted with an Error? that should make your life easier next time you have to debug a similar case.
I still haven't had a good look into the bug, but I have finally got the time to spend on it now, and have reproduced it. So look for a fix by the end of the day (I hope).
--
This signature intentionally left boring.
Eric Blake [EMAIL PROTECTED]
BYU student, free software programmer
_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
