Coding guidelines - noncopyable

From: Peter Dimov (pdimov_at_[hidden])
Date: 2001-07-07 05:57:58

I disagree with the 'noncopyable' guideline. Here's why:

* Deriving from noncopyable invokes warnings/remarks from MSVC and Intel
C++. In order to suppress them, I have to declare the copy constructor and
the assignment operator private, which defeats the purpose.

* In order to derive from boost::noncopyable, I have to introduce a
dependency on boost/utility.hpp. Since headers with such names tend to
change frequently, this means frequent recompilations for no apparent
reason.

--
Peter Dimov
Multi Media Ltd.