Is there a reason why jdbm defines the FastIterator class, rather than simply using the standard Iterator interface?
I'd be happy to prepare a patch that would eliminated FastIterator, replacing its usage with Iterator, and properly implementing hasNext. This would only impact HashDirectory as far as I can tell, but would help eliminate what appears to be a wart (IMO) in the library. (Maybe jdbm predates Java 1.2, so Iterator wasn't available?) Would such a patch be welcome? Thanks, - Chas ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Jdbm-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdbm-general
