A multi-threaded object-oriented programming model
Pages 83 - 86
Abstract
This paper presents a concurrent object-oriented programming (COOP) model established around concurrent objects which may have a body. Once an object with a body is created, its body begins to run as a separate execution thread of the object. Distinguished from some active-object-based concurrent object-oriented models, the object body in our model is not used for the concurrency control of objects, but only as a mechanism to introduce concurrent executions into OO model. Concurrency control is specified by the attributes of objects and the control codes are generated by a compiling system based on these attributes. In addition, objects should be designed in such a way that they can be used in both sequential and concurrent environments, no matter whether they have a body or not. In our model, several execution threads may coexist in an object and some synchronization mechanisms are provided to control the concurrent executions of these threads. The paper presents two examples of concurrent programming with our model.
References
[1]
[1] Agha G., Concurrent Object-Oriented Programming, CACM, 33(9), Sept., 1990.
[2]
[2] Andrews G. R. and F. B. Schneider, Concepts and Notations for Concurrent Programming, Computing Surveys, Vol. 15, No. 1, March 1983.
[3]
[3] America P., POOL-T: A Parallel Object-Oriented Language, In A. Yonezawa and M. Tokoro, editors, Object-Oriented Concurrent Programming, MIT Press, 1987.
[4]
[4] Caromel D., Toward a Method of Object-Oriented Concurrent Programming, CACM 36(9), Sept., 1993.
[5]
[5] Chen J. J. and G. L. Zheng, NDC++: An Approach to Concurrent Extension of C++, ACM SIGPLAN Notices, Vol. 32(3), March, 1997.
[6]
[6] Matuoka S. and A. Yonezawa, Analysis of Inheritance Anomaly in Object-Oriented Concurrent Programming Languages, In G. Agha, etc., editors, Research Directions in Concurrent Object-Oriented Programming, MIT Press, 1993.
[7]
[7] Meyer B., Systematic Concurrent Object-Oriented Programming, CACM 36(9), Sept., 1993.
[8]
[8] Nierstrasz O., Composing Active Objects, In G. Agha, etc., editors, Research Directions in Concurrent Object-Oriented Programming, MIT Press, 1993.
[9]
[9] Nierstrasz O. and M. Papathomas, Viewing Objects as Patterns of Communicating Agents, ECOOP/OOPSLA '90.
[10]
[10] Nensins C., Synchronizing Actions, Proc. of ECOOP'91, Geneva, Switzerland, LNCS, 512, Springer Verlag, July, 1991.
[11]
[11] Papathomas M., Language Design Rationale and Semantic Framework for Concurrent Object-Oriented Programming, Ph.D. dissertation, Universite de Geneve, 1992.
[12]
[12] Tomlinson C. and V. Singh, Inheritance and Synchrozization with Enabled-Sets, Proc. of OOPSLA'89, Vol. 24, pp. 103-112. SIGPLAN Notices, ACM Press, Oct. 1989.
[13]
[13] Yonezawa A., et al, Modelling and Programming in an Object-Oriented Concurrent Language ABCL/1, In A. Yonezawa and M. Tokoro, editors, Object-Oriented Concurrent Programming, MIT Press, 1987.
Index Terms
- A multi-threaded object-oriented programming model
Recommendations
Deadlock freedom through object ownership
IWACO '09: International Workshop on Aliasing, Confinement and Ownership in Object-Oriented ProgrammingActive objects are an attractive method of introducing concurrency into Java-like languages by decoupling method execution from invocation. In this paper, we show how ownership is used in the Java [14] subset language CoJava [17] to prevent deadlock ...
Efficient and reasonable object-oriented concurrency
PPoPP 2015: Proceedings of the 20th ACM SIGPLAN Symposium on Principles and Practice of Parallel ProgrammingMaking threaded programs safe and easy to reason about is one of the chief difficulties in modern programming. This work provides an efficient execution model and implementation for SCOOP, a concurrency approach that provides not only data-race freedom ...
Transactions for concurrent object-oriented programming systems
Proceedings of the ACM SIGPLAN Workshop on Object-Based Concurrent ProgrammingConcurrent object-oriented programming systems (COOPS) require support for fault tolerance, concurrency control, consistent commitment of changes and program-initiated rollback. It is sometimes suggested that the classical transaction processing model ...
Comments
Please enable JavaScript to view thecomments powered by Disqus.Information & Contributors
Information
Published In
Copyright © 1998 Authors.
Publisher
Association for Computing Machinery
New York, NY, United States
Publication History
Published: 01 May 1998
Published in SIGSOFT Volume 23, Issue 3
Check for updates
Author Tags
Qualifiers
- Article
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- 0Total Citations
- 319Total Downloads
- Downloads (Last 12 months)46
- Downloads (Last 6 weeks)12
Reflects downloads up to 21 Nov 2024
Other Metrics
Citations
View Options
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in