The Adapter design pattern provides a solution:
Define a separate Adapter class that converts the interface of a class (Adaptee)
into another interface (Target) clients require.
Work through an Adapter to work with classes that have not the required interface.
Describing the Adapter in more detail is the theme of the following sections.
See Applicability section for all problems Adapter can solve.

• The key idea in this pattern (object version) is to work through a separate Adapter object that adapts the interface of an (already existing) object.
  Clients do not know whether they are working with a Target object or an Adapter.
• There are two ways to define an Adapter:
  • Class Adapter: Uses inheritance to implement a Target interface in terms of (by inheriting from) an Adaptee class.
  • Object Adapter: Uses object composition to implement a Target interface in terms of (by delegating to) an Adaptee object (adaptee.specificOperation()).
  • A class adapter commits to (inherits from) an Adaptee class at compile-time. An object adapter is more flexible because it commits (delegates) to an Adaptee object at run-time (see also Sample Code / Example 1).
  • There exists a wide range of possible adaptations, from simply changing the
    name of an operation to supporting an entirely different set of operations.
• Built-in interface adaptation.
  To make a class (Adaptee) more reusable, it can be configured with an adapter object that converts the interface of the class into the interface clients (that want to reuse the class) require.