Subject: Re: [boost] [config] New NO_COPYABLE, DELETE_COPY_CTOR and DELETE_COPY_ASSIGN macros
From: Vicente Botet (vicente.botet_at_[hidden])
Date: 2012-05-11 09:58:27
Olaf van der Spek-3 wrote
> On Tue, May 1, 2012 at 9:50 AM, Vicente J. Botet Escriba
> <vicente.botet@> wrote:
>> As these come together quite often when we want to make a non copyable
>> the user can use instead
>> Â public:
>> Â Â BOOST_NO_COPYABLE(CLASS)
> Isn't it simpler to derive from boost::noncopyable?
I want to avoid to derive from whatever class.
-- View this message in context: http://boost.2283326.n4.nabble.com/config-New-NO-COPYABLE-DELETE-COPY-CTOR-and-DELETE-COPY-ASSIGN-macros-tp4600307p4626504.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk