Disadvantages of oop

Answer 1

On giving a practical example to show the difference between saying and real world working.in designing a car model using oop use classes and inheritance but this is not the same as desire.problem will arise when modues increases and line of code shoot up as in the case of Mercedes-Benz S-Class car with 50 controllers, 600,000 lines of code, hundreds of bus messages, thousands of signals, and three networks.

An other issue Aries during athis talk be iterface for all different subsystems which is not possible to same location as assumed by OOP .Different sunsystems use different approaches and methods to deal with problem and they are inheriently built for this .If desire to have same interface changes must br done at subsystm level this will loss their imprtance.

Instead of diving class and making inheritance industry use different approach they divide subsystems ansd made a small team for each subsystem. There is a need for talented systems

engineers to specify and integrate the subsystems, but there is no overall grand software design where OOP might help.

Answer 2

Personally I find oops code can get very hard to read, even well written code. The problem is inheritance and polymorphism. The problem with inheritance is that if you want to figure out what a given method does, you have to search up the class hierarchy until you find its definition. In a way, inheritance is worse than goto--at least with goto the destination is somewhere in your function but with inheritance it could be in any number of files. The problem with polymorphism means that simply finding a function with the right name is not sufficient, you have to also look at the parameters. Trying to read code without a good class browser is almost impossible. It IS impossible once you get into virtual functions where the decision of which function gets called is only determined at runtime. For example, suppose you're trying to figure out the following line of code obj.Write(a);. Which function is being called? Well, if you're lucky and you know what type obj is then you probably only have about 10 different versions of Write() to pick from depending upon what a is. If you're unlucky and obj can be of several types, then you got a lot of work cut out for you. Two other oops features that can get really hard to read are operator overloading (fortunately it's rarely used), and class properties that look like simple variable assignment but are really complex function calls. My very first exposure to oops programming was as an intern at Sun Labs (just downstairs from the tcl team) where my job was to instrument C++ kernel code to determine where time was being spent. Kernel programming is hard enough, but the real bear was just trying to read the well-written but deeply inherited code. Mohanjeet Singh mohanjeet_rjp@Yahoo.com