Regarding: "I am trying to find a reason why someone would define types while not referring to them. The only one I see is for method overloading."
Here is another reason: using Collection classes that lose the type information of the items they contain. That type information needs to be handed to the client somehow, even though the type is not referenced in the interface being serialized. Bob Woodley ------- Original Message ------ Tom, IMO, your statement is true except in the context of method overloading. I am trying to find a reason why someone would define types while not referring to them. The only one I see is for method overloading. This being said, I don't see any harm in generating extra classes. Certainly not when they are indirectly referenced, thus, meant to serve a purpose. I guess I am a good developer, I am lazy, I like code generators! -- Sylvain. __________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/
