Trollhorn wrote:I assume you mean the Iterable interface.
So far, I have no experience in classloading, annotations and annotation processing... as a little exercise, I thougt of a little app that does the following:
It dynamically loads classes (Collections, specifically) which
a) implement the Iterator interface
b) "have" annotations to mark the methods for insertion, removal (@insert, @remove or whatever)Well, seeing as all the non-Map collections implement Collection, you don't really need any fancy processing, but i guess it could be fun...
Trollhorn wrote:wouldn't it still make sense for them to write collection implementations which implement Collection? it's not too difficult seeing as they can just extend AbstractCollection and would only need to implement the methods you have mentioned anyway.
well, it's actually not meant for the Java Collections Framework but for the data structures students implement for practice in Data Structure courses, so that they don't have to write ugly console apps to test or play around with their programs :-).