> Forget I<Whatever>. It breaks sorting and it is allows people to avoid thinking if the interface is necessary or not. 100%. Any "structure definition" shoul

> Forget I<Whatever>. It breaks sorting and it is allows people to avoid thinking if the interface is necessary or not. 100%. Any "structure definition" should be assumed to be an interface, and any explicit separation of definition and implmentation should be deferred until multiple variants are required. My Java projects and files were corked up with Ifiles that only ever had a single implementation. Caveat: I've only worked on internal projects, explicit interfaces are much more useful for something widely shared. Don't use the I<Class> convention though.