RE: [boost] Threads

From: Michael H. Cox (mhcox_at_[hidden])
Date: 2000-08-01 20:43:16

If you're going to write a thread library, you might want to look at how the
ACE library does it (they support Win32 and UNIX (I think, pthreads)).
We're using RW's Threads.h++ at work which they acknowledge was based on a
lot of ideas from ACE.  It would be nice to have a thread library that was
more standards based than Threads.h++ and took more advantage of the latest
C++ features.

> -----Original Message-----
> From: Joe Gottman [mailto:joegottman_at_[hidden]]
> Sent: Tuesday, August 01, 2000 8:36 PM
> To: boost_at_[hidden]
> Subject: Re: [boost] Threads
>
>
> Since threads, mutexes, etc. are very dependent on the local architecture
> for their implementation, I think it would be a good idea to
> define a basic,
> minimal interface for each, similar to the iterator interface used in the
> STL.  This would allow users to write portable template classes and
> functions parameterized on the thread, lock or whatever.  For instance, a
> thread safe Singleton template would be extremely useful.
>
> Joe Gottman
> ----- Original Message -----
> From: William Kempf <sirwillard_at_[hidden]>
> To: <boost_at_[hidden]>
> Sent: Tuesday, August 01, 2000 4:41 PM
> Subject: [boost] Threads
>
>
> > We had some interesting discussions going on about a thread library
> > for boost for a while.  However, the subject seems to have died,
> > which I find to be very unfortunate.  There's a lot of interest in a
> > good C++ thread library, with interesting discussions going on in
> > several places online.  So, I'm going to try and regenerate some
> > debate on here by discussing my own thoughts.  I should mention that
> > I'm familiar with threaded programming, having implemented some
> > thread libraries myself and done a fair amount of threaded coding,
> > but I'm far from an expert so a lot of what I have to say may be
> > obvious or even not a good idea.
> >
> > Someone else wanted to start with the primitive types that should be
> > defined, so I'll start there.  The primitives I think that should be
> > defined as class objects:
> >
> > thread
> > mutex
> > semaphore
> > condition
>
>
>
>
>
>