"Peter Dimov" <pdimov@mmltd.net> wrote in message news:001001c54ab9$32f6d6d0$6401a8c0@pdimov2... | Thorsten Ottosen wrote: | > because you had to put "polymorphic" in front of "value" to describe | > what it means; | > polymorphic objects don't have value-based copy-semantics; you can't | > provide meaningful copy-constructor | > and copy-assignment operators. | | A cloning pointer holding a polymorphic object is CopyConstructible and | Assignable. Why is this not meaningful? it could be, but know you're not talking about the original, wrapped polymorphic object. | A vector of cloning pointers is also CopyConstructible and Assignable. cool, then use that if you need to; but without move-semantics you're gonna pay performance wise. -Thorsten