Why should the “PIMPL” idiom be used? [duplicate]

by

I think most people refer to this as the Handle Body idiom. See James Coplien’s book Advanced C++ Programming Styles and Idioms. It’s also known as the Cheshire Cat because of Lewis Caroll’s character that fades away until only the grin remains.

The example code should be distributed across two sets of source files. Then only Cat.h is the file that is shipped with the product.

CatImpl.h is included by Cat.cpp and CatImpl.cpp contains the implementation for CatImpl::Purr(). This won’t be visible to the public using your product.

Basically the idea is to hide as much as possible of the implementation from prying eyes.

This is most useful where you have a commercial product that is shipped as a series of libraries that are accessed via an API that the customer’s code is compiled against and linked to.

We did this with the rewrite of IONA’s Orbix 3.3 product in 2000.

As mentioned by others, using his technique completely decouples the implementation from the interface of the object. Then you won’t have to recompile everything that uses Cat if you just want to change the implementation of Purr().

This technique is used in a methodology called design by contract.

More Related Contents:

  1. Is the PIMPL idiom really used in practice?
  2. Which access specifiers will not affect a friend function?
  3. Does the stream operator exist for class member functions?
  4. Why should I prefer to use member initialization lists?
  5. When should you use a class vs a struct in C++?
  6. Is there a performance difference between i++ and ++i in C++?
  7. Thou shalt not inherit from std::vector
  8. How to call a parent class function from derived class function?
  9. What is the difference between private and protected members of C++ classes?
  10. Separating class code into a header and cpp file
  11. Vectors and polymorphism in C++
  12. What is the point of a private pure virtual function?
  13. Why can’t a derived class call protected member function in this code?
  14. How do I use unique_ptr for pimpl?
  15. Implementing multiple interfaces in c++
  16. The Pimpl Idiom in practice
  17. What is the difference between a concrete class and an abstract class?
  18. Diamond inheritance (C++)
  19. overloading base class method in derived class
  20. Semicolon after class declaration braces
  21. Pimpl idiom vs Pure virtual class interface
  22. C++ inheritance and member function pointers
  23. Should I use public or private variables?
  24. How to initialize the reference member variable of a class?
  25. Making a vector of instances of different subclasses
  26. How to create class objects dynamically?
  27. What is the purpose of forward declaration?
  28. Why should I prefer to use member initializer lists?
  29. What does slicing mean in C++?
  30. Free function versus member function

Leave a Comment