Wrapping a third-party library

• A

  Always, since depending on external code is a risk

• B

  Only when a replacement is already planned

• C

  When the library touches many places, or its interface does not suit the domain

• D

  Whenever the library has an unstable API that keeps changing between versions