24 Mar
2012
24 Mar
'12
10:22 p.m.
On Sat, Mar 24, 2012 at 11:01:30AM -0500, John M. Dlugosz wrote:
On 3/21/2012 2:18 AM, Igor R wrote:
To get more helpful error, declare a private copy-ctor& assignment operator in your class - and you'll see who attempts to copy.
That's what I did. So is there anything that boost::noncopyable does for me beyond that, or did I just make it totally redundant?
The downside of the private declare-and-not-implement is that if the copy attempt is in a member function or friend, the error does not surface until linking time, where all the context of use is completely obliterated. -- Lars Viklund | zao@acc.umu.se