hoping the grandmaster could shed some light. A very high review is that I'm not new to coding, but still new to OOP. This set of message classes is at the core of the large modeling application we are writing, and I don’t want to do it stupidly - this interface cuts the application in half, from the sequencer to the executor and vice versa.
My question is whether there is a bad idea to have a hierarchy of inheritance of this depth (the image is not yet specified, it may end at the end of 5 or 6). This is in contrast to the fact that some of the child classes simply have a directed connection with their parent class, and do not inherit.
I read that a deep inheritance hierarchy is not a good idea, and that if a child class inherits just to have parent data, then you should just include the parent as data in the child element, but I can hardly hug me around. What bad thing will happen to us if I decide to make the hierarchy of inheritance 7 deep or something like that? Obviously, a small hit on performance, and changing things at the top of the hierarchy will have a huge ripple throughout the application, but apart from that, I see no problem. In addition, I am a little worried about minor differences in performance.
( : , ? , , . , , , , 10 000 .)
( № 2: , , -? .)