>Sometimes, however, you would not subclass to not make too deep hierarhy and keep your libraries light.

Yeah, I guess if your not careful you can go "class crazy" and end-up with your code all over the place. Seems like there can be a fine line between a "functional hierarchy" and going "too deep."

>For instance, I suggested to add some conditional piece of code in our baseform class. For me it sounded silly to repeat it all over again in all my apps.

And that's a great examply of my issue exactly. If the functionality in the base class could be applied to all apps that the library supports, shouldn't the logic be allowed?

>However, as it was for most of my suggestions, they were not implemented...

Sorry to hear that. With other posts you've made in the past, and this one, it sounds like a restrictive work environment.