> And good, consistent naming of classes and > other identifiers is a non-trivial aspect of good design and coding, > especially in publicly used parts of frameworks
True, but imho that has more to do with choosing names that communicate what things do well, not so much whether there are certain prefixes or postfxes. > understanding from the original posts on this thread is that the technique > described to incrementally get rid of I* interfaces by deprecating and > eventually removing "offending" I* interfaces is exactly the right way to > make such an improvement with minimal disruption. There's one thing I hate more than making unnecessary API breaks, and that is accompanying them with annoying deprecation warnings :-) Eelco
