This week's book giveaway is in the Cloud/Virtualizaton forum.
We're giving away four copies of Mesos in Action and have Roger Ignazio on-line!
See this thread for details.
Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

OOAD Java

 
Vishva Rajput
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When we implement an OOAD design in Java , is there something we wish Java had that would make this implementation easier? In other words what do we feel java should have had that would have made OOAD implementation easier. One thing i can think of is support for mulitiple inheritance???Are there more?
 
John Smith
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One thing i can think of is support for mulitiple inheritance???
Multiple inheritance was omitted from Java on purpose, -- it was determined that it causes more problems and confusion than it helps in OOD, so this is not a good example. Many other aspects of Java, such as exception handling, garbage collection, collections framework, Swing, not to mention the portability and the single rooted object hierarchy, are all about clarity and simplicity. Java encourages you to write OO code by its design. If you were an allien, which code would you rather extend, maintain, and support, -- C++ with its multiple inheritance and the "**&&" surrounding the object references or Java with its well thought concept of separation between the interfaces and the implementations?
[ December 05, 2003: Message edited by: Eugene Kononov ]
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Eugene Kononov:
C++ with its multiple inheritance and the "**&&" surrounding the object references or Java with its well thought concept of separation between the interfaces and the implementations?

Aren't you mixing different things here? What does MI have to do with "**&&" syntax for object referencing and separation between interfaces and implementation?
 
John Smith
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
IP: Aren't you mixing different things here? What does MI have to do with "**&&" syntax for object referencing and separation between interfaces and implementation?
You are right, I did throw the syntax issue to the mix. However, it does address the original question, -- "**&&" certainly doesn't help in OOD.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic