> should look at the horrible C++ code in 
> btree..
 
It's not really horrible code, it's just old-style Bjarne C++. Remember, it
was written long before ANSI codified C++.
 
That said, bringing it up to snuff is certainly a worthwhile exercise! If
you're working on it, be *very* careful not to introduce/remove odd side
effects, etc. God knows what's going on in there. ;)
 
BTW, if you start making major changes, it probably means that you're
taking the time to understand how some of the functions work (at least it
had better :) .. As you're doing so, can you document your findings in
Doxygen (similar to JavaDoc) format? I will add some documentation
standards information in the HACKING file this week.
 
Wes

--- Maximus/2 3.01