Boost logo

Boost :

From: Matt Calabrese (rivorus_at_[hidden])
Date: 2006-05-01 13:05:09

Thanks, I will be looking into the interfaces provided.

For clarity, atomic types in my library are currently all
internally emulated with a thread-safe active type implementation using an
immediate act model which automatically forces a wait prior to returning
(see my linked doc in the original post for what active types and act model
are specifically with respect to the library). Clearly this is not very
efficient particularly for built-in
types, but it is the simplest implementation to get up and running in
a fairly portable manner
which accounts for user-defined types with a well-defined active interface.
That being said, the main goal of atomic types in my library (which is only
a small part of the library) is to provide an easy way to create thread-safe
user-defined types of any complexity, which serialize all operations upon
them and are accessed through any interface provided by means described in
the documentation. This allows programmers to create complex types and
easily have a way to safely use instances of them by multiple threads at the
same time and have the operations not return until the call completes as
though all operations were atomic. Of course, for built-in types
specifically, more efficient techniques can be used
internally, but that is not of primary concern at this point. Really,
the focus of the library is for the creation of parallel loops and
active functions and active types, with atomic types provided as a
simple adapter for active types.

-Matt Calabrese

Boost list run by bdawes at, gregod at, cpdaniel at, john at