[Mono-list] Re: IEnumerators

[John Barnette]

> Also, I think, there ought to be the sort of "skeleton" for all
> collections
> classes, because they share a great deal of functionality and behaviour,
> Enumerators for example. Not necessary some code snippet but a
> set of rules,
> like these for Enumerators and corresponding tests-cases to check the
> implementation. Any ideas?

> Also, I think, there ought to be the sort of "skeleton" for all
> collections
> classes, because they share a great deal of functionality and behaviour,
> Enumerators for example. Not necessary some code snippet but a
> set of rules,
> like these for Enumerators and corresponding tests-cases to check the
> implementation. Any ideas?

Maybe it'd be worthwhile to write NUnit test classes for interfaces like
ICollection and subclass 'em for implementations like ArrayList or
Hashtable.  This is awkward, of course, since there's no multiple
inheritance (for a class that implements IList and ICollection, f'rexample),
but we might be able to figure out some sort of coherent approach.


~ j.  // I WILL learn to love writing unit tests.  I WILL learn to love
writing unit tests.