1 Jun
2016
1 Jun
'16
12:03 a.m.
On 1/06/2016 11:55, Emil Dotchevski wrote:
Not in the public interface, but they would exist in the private implementation. Encapsulation is great, all that goodness with constructors establishing invariants, member functions maintaining invariants, exceptions enforcing postconditions -- it's all good, but it is now an implementation detail; all that code lives in the CPP file.
Of course.
Moving is not really an issue -- you can move the shared_ptr instead. The same applies to shallow copying (copying the pointer rather than the underlying object).
Yes, but that's different. It's more precise to say that one can't move or copy an incomplete type.
I did say that.