- it accepts an array of classes to match several classes
- the class matching can optionnaly be "strict", that is subclasses of the required class aren't returned. In strict mode a ClassFilterIterator will only return objects of the same class (i.e. equals() == true) or objects implementing the interface (but not inheriting an implementation).
I removed the default Object.class matching when the specified class is null (the evaluate method will throw a NPE) and made the predicate public so that it can be reused until it is moved to a more sensible home for predicates.
Only the ClassPredicate is really interesting here, i agree with Rich that there is no real need to subclass the FilterIterator class. I just hope the lang/functor/collections debate will reach an end soon ;)
Emmanuel
ClassFilterIterator.zip
Description: Zip compressed data
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
