Parallel object monitors

Abstract

Coordination of parallel activities on a shared memory machine is a crucial issue for modern software, even more with the advent of multi-core processors. Unfortunately, traditional concurrency abstractions force programmers to tangle the application logic with the synchronization concern, thereby compromising understandability and reuse, and fall short when fine-grained and expressive strategies are needed. This paper presents a new concurrency abstraction called POM, parallel object monitor, supporting expressive means for coordination of parallel activities over one or more objects, while allowing a clean separation of the coordination concern from application code. Expressive and reusable strategies for concurrency control can be designed, thanks to a full access to the queue of pending requests, parallel execution of dispatched requests together with after-actions, and complete control over reentrancy. A small domain-specific aspect language is provided to adequately configure pre-packaged, off-the-shelf synchronizations.This work is partially funded by the Conicyt-INRIA project OSCAR, and the CoreGRID EU Network of Excellence. ´ E. Tanter is partially funded by the Millennium Nucleus Center for Web Research, Grant P04-067-F of Mideplan, Chile, as well as by the FONDECYT Project 11060493

Why inheritance anomaly is not worth solving

“…When τ, σ ∈ Types then σ is a subtype of τ iff beh τ beh σ. Further in our discussion, we use the function imp : Class → Types that return the type τ ∈ Types that is im- 4 This condition is a prerequisite for the safety preservation in Section 3.3.…”

“…Object-oriented programming appears as the paradigm of choice to simplify concurrent programming [4,12,14,24,36], however, concurrent object-oriented programming (COOP) remains a difficult task. Many COOP languages are prone to what is called inheritance anomaly [25].…”