pimpl-idiom

问题 PIMPL stands for P ointer to IMPL ementation. The implementation stands for \"implementation detail\": something that the users of the class need not to be concerned with. Qt\'s own class implementations cleanly separate out the interfaces from the implementations through the use of the PIMPL idiom. Yet, the mechanisms provided by Qt are undocumented. How to use them? I\'d like this to be the canonical question about \"how do I PIMPL\" in Qt. The answers are to be motivated by a simple

问题 This question already has an answer here: Is the pImpl idiom really used in practice? 11 answers Backgrounder: The PIMPL Idiom (Pointer to IMPLementation) is a technique for implementation hiding in which a public class wraps a structure or class that cannot be seen outside the library the public class is part of. This hides internal implementation details and data from the user of the library. When implementing this idiom why would you place the public methods on the pimpl class and not the

问题 I am reading the book \"Exceptional C++\" by Herb Sutter, and in that book I have learned about the pImpl idiom. Basically, the idea is to create a structure for the private objects of a class and dynamically allocate them to decrease the compilation time (and also hide the private implementations in a better manner). For example: class X { private: C c; D d; } ; could be changed to: class X { private: struct XImpl; XImpl* pImpl; }; and, in the CPP, the definition: struct X::XImpl { C c; D d;