Boost C++ Libraries: Ticket #11141: boost::noncopyable does not prevent adding copy constructor to derived class

attachment set

Wed, 25 Mar 2015 09:59:45 GMT

attachment → test_noncopyable.cpp

class deriving boost::noncopyable and declaring copy constructor

component changed; owner set

viboes — Thu, 26 Mar 2015 07:26:44 GMT

owner set to No-Maintainer
component None → utility

Marshall Clow — Thu, 26 Mar 2015 15:24:55 GMT

My opinion on this is "close as not a bug".

We don't prevent people from acting maliciously.

noncopyable makes the copy constructor and assignment operators private (and doesn't implement them), so if you call them you get a compile (or link) error. If you go and implement your own copy constructor in a class that is derived from noncopyable, then my belief is that you wanted to be able to copy those objects.

Tue, 31 Mar 2015 08:09:14 GMT

Yup, seems I got the semantics wrong, boost::noncopyable is a macro, that spares some typing. I still have to ensure Foo contains no copy constructor, I hoped it would free me from checking that as well.

I retire the question

attachment set

Tue, 31 Mar 2015 08:13:45 GMT

attachment → test_noncopyable2.cpp

boost::noncopyable correctly working

status changed; resolution set

Marshall Clow — Wed, 01 Apr 2015 22:16:11 GMT

status new → closed
resolution → invalid

Not really a macro - but a class that you inherit from to get certain behavior.

Because the behavior is inherited, you can override it if you choose.