Re: Boost.Threads - thread_desc concept

From: williamkempf_at_[hidden]
Date: 2001-06-27 14:10:23

--- In boost_at_y..., Jeremy Siek <jsiek_at_r...> wrote:
> On Wed, 27 Jun 2001 williamkempf_at_h... wrote:
> > --- In boost_at_y..., "Greg Colvin" <gcolvin_at_u...> wrote:
> > > From: <williamkempf_at_h...>
> > > > Considering all of the discussion so far, I think this 
slightly
> > > > modified interface is the best design so far:
> > > >
> > > >     class thread : boost::noncopyable
> > > >     {
> > > >     public:
> > > >         thread(detail::threadproc proc); // Starts the thread
> > > Do I have to reach down into thread::detail to declare my
> > > proc, or will this eventually be templatatized to take any
> > > function or function object of zero arguments?
> >
> > No, you never directly use anything from detail namespaces.  In 
this
> > case detail::threadproc is just a typedef to 
boost::function1<void>.
> > This already qualifies any function or function object taking zero
> > arguments as valid.
> 
> Then the interface of the constructor should be specified as taking
> boost::function1<void> and not detail::threadproc.

Historical artifact.  I'll change it before we go to submission.

Bill Kempf