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

From: Fisher; Damien Kaine (dfisher_at_[hidden])
Date: 2001-09-04 00:03:00

sorry, I was being vague.

RC would be the refcounting.

so instead of count++, you would have an object of type RC, say rc, and go
rc.add(), etc.

On Tue, 4 Sep 2001, AlisdairM wrote:

> What is gained by doing this though?  The template parameter is never used.
> 
> Or am I missing something?
> 
> AlisdairM
> 
> -----Original Message-----
> From: Fernando Cacciola [mailto:fcacciola_at_[hidden]]
> Sent: 03 September 2001 21:45
the template parameter 
> To: boost_at_[hidden]
> Subject: RE: [boost] Documenting non-copyable-ness (was: Re: Review:
> Boost.Threads)
> 
> I'll take this opportunity to ask this question:
> Why isn't noncopyable a template class?
> 
> That is:
> 
>     template<class T>
>     class noncopyable
>     {
>     protected:
>         noncopyable(){}
>         ~noncopyable(){}
>     private:  // emphasize the following members are private
>         noncopyable( const noncopyable& );
>         const noncopyable& operator=( const noncopyable& );
>     }; // noncopyable
> 
> 
> Used as:
> 
> struct Some : boost::noncopyable< Some>
> {
> ...
> };
> 
> 
> Info: http://www.boost.org  Unsubscribe: <mailto:boost-unsubscribe_at_[hidden]> 
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
> 
>