[cpp-threads] High-level concurrency issues

[Herb Sutter]

I wrote:
> BTW, I know I'm alluding to Concur without explaining what it is -- I
> only showed it publicly for the first time last month, so it's new to
> the world.

Cool -- they just made the video of my talk about Concur available
online. The link is:

http://microsoft.sitestream.com/PDC05/TLN/TLN309_files/Default.htm#nopre
load=1&autostart=1

Comments/criticisms/kudos/arrows/etc. welcome. Thanks,

Herb


> The basic summary is that Concur aims to:
> 
>   define higher-level abstractions (above "threads+locks")
> 
>   for today's imperative languages (first C++, but applicable to
others)
> 
>   that evenly support the range of concurrency granularities
>     (e.g., coarse-grained out-of-process, long-lived in-process,
>     loop/data parallel, all with a similar programming model)
> 
>   to let developers write correct and efficient concurrent apps
>     (that they can reason about easily and that is toolable)
> 
>   with lots of latent parallelism (and not lots of latent bugs)
> 
>   mapped to the user's hardware to reenable the free lunch (exes that
> run
>     well on 1- and 2-core, better on 8-core, better still on 64-core,
> etc.).
> 
> I can't easily describe more than that in email. I could show more
about
> it sometime when we could get together. No papers yet.
> 
> Herb
> 
> 
> --
> cpp-threads mailing list
> cpp-threads at decadentplace.org.uk
> http://www.decadentplace.org.uk/cgi-bin/mailman/listinfo/cpp-threads