Originally posted by v ray:
Pretty impressive. However, I am not very clear about the need for this or how one would go about implementing similar changes for a a real-time project.
An example? At the moment I'm working on an economical calculation engine. Generics (and Mark Interfaces to be honest..) helped us a lot in reducing code, make it clearer, safer, flexible.
Originally posted by v ray:
1. Would I try to make only the abstract classes generic?
I agree with Jesper, you are not forced in any way to do that. But, at least in the project above, I found very useful implementing almost all the logic in ABSTRACT classes making a VERY VERY VERY heavy use of generics and interfaces. We created then a bunch of specific implementation where we make the generics concrete (hiding so the complexity of the structure for the "low-level-developer"), class declarations easier to read/write and so on
Originally posted by v ray:
3. What are the usual areas where such generic classes are most useful?
MY OPINION is that they are more useful in containers, rules defining/executing classes, utilities class. Especially if their use is closely bound to interfaces.
Don't hesitate to ask for more details if you want