Choosing composition vs. inheritance

Bruce Eckel's Thinking in Java Contents | Prev | Next

vs. inheritance

// Composition with public objects
class Engine {
  public void start() {}
  public void rev() {}
  public void stop() {}
class Wheel {
  public void inflate(int psi) {}
class Window {
  public void rollup() {}
  public void rolldown() {}
class Door {
  public Window window = new Window();
  public void open() {}
  public void close() {}
public class Car {
  public Engine engine = new Engine();
  public Wheel[] wheel = new Wheel[4];
  public Door left = new Door(),
       right = new Door(); // 2-door
  Car() {
    for(int i = 0; i < 4; i++)
      wheel[i] = new Wheel();
  public static void main(String[] args) {
    Car car = new Car();
} ///:~ 

Because the composition of a car is part of the analysis of the problem (and not simply part of the underlying design), making the members public assists the client programmer’s understanding of how to use the class and requires less code complexity for the creator of the class.


  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date