> I'll be glad if I never have to see PIMPL ever again. It makes tracking down the actual implementation of some functionality so much harder than it has to be.

> I'll be glad if I never have to see PIMPL ever again. It makes tracking down the actual implementation of some functionality so much harder than it has to be. Not really. There are two main flavours of pimpls: one where the impl class is a pod that only holds member variables, and one where the impl class holds both member variables and private member functions. On both, the implementation can and does stay in the very same translation unit. On the former, the code stays in the very same class,without any change. You only experience the sort problems you describe if you bring them upon yourself. That's hardly the idiom's fault.