From: Caleb Epstein (caleb.epstein_at_[hidden])
Date: 2005-10-04 11:15:13
On 10/4/05, Rob Stewart <stewart_at_[hidden]> wrote:
> For pimpl to work, the implementation class must be complete when
> you try to use it. No library can eliminate that.
Or the Interface class provides methods that forward to the Implementation
The pimple library automates the memory management, including
> during copying and copy assignment, so you don't have to. Thus,
> you declare a pimpl object and, in the process, forward declare
> your impl type, and in exchange, you get automated memory
> management. Where's the problem?
I guess my problem is one of terminology. In my mind, a Pimpl class holds
the pointer to the Implementation as well as providing the methods that
forward to the Implementation. This implementation only holds the pointer
and manages the memory, which makes me think it should be called a
PimplHolder, and not a Pimpl.
-- Caleb Epstein caleb dot epstein at gmail dot com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk