Re: [boost] Documenting non-copyable-ness (was: Re: Review: Boost.Threads)

From: Anatoli Tubman (anatoli_at_[hidden])
Date: 2001-09-04 11:44:36

On Tuesday 04 September 2001 16:36, Fernando Cacciola wrote:
> class Foo : noncopyable {} ;
> class Bar : noncopyable {} ;
>
> Those two classes are *completely unrelated*, yet they belong to the same
> hierarchy.
> This fact -the conceptually wrong hierarchical relation between them- is
> messy and a very subtle source of problems; even though most applications
> will hide this.
>
> Messy because in a graphical class browser everything is rooted at
> noncopyable.

A graphical class browser that shows you private bases by default
probably should be approached with a sledgehammer.

> Error prone (very subtle) because, as it was expressed, one can manage both
> classes through a noncopyable*.

What can you do with noncopyable* that you can't do with void*?
(I know, I know: pointer arithmetic! :)

-- 
anatoli at ptc dot com -- opinions are mine