[cpp-threads] C++ committee meeting in Mont Tremblant

[Alexander Terekhov]

On 10/10/05, Hans Boehm <Hans.Boehm at hp.com> wrote:
[...]
> Among that group, people seemed to favor a similarly structured interface,
> with a C-level API (fixed set of types, ordering constraints part of
> operation names) at the bottom, with a higher-level C++ API implemented on
> top of it.

I believe that <cthread>/<pthread.h> WRT <thread> (including atomic<> stuff)
ought to be just like  <iohw.h> WRT <hardware> (C++ performance TR stuff).
Quoting "Appendix C" (http://www.research.att.com/~bs/performanceTR.pdf):

<quote>

The implementation of the basic <iohw.h> hardware register access interface
on top of the <hardware> interface is mainly straightforward. This section
provides an example of how such an implementation can be achieved.

The purpose of using C++ at the lowest level is to take advantage of
compile-time evaluation of template code to yield object code specialized
for specific hardware. For a good implementation of the basic templates that
perform the lowest-level hardware access operations, this approach typically
leads to code that maps directly to machine instructions as efficient as
code produced by an expert programmer. Additionally, the type safety of the
C++ interface minimizes debugging and errors.

</quote>

regards,
alexander.

P.S. http://groups.google.com/group/comp.std.c++/msg/158390632f4667fb