Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 725 papers for “Concurrent object-oriented programming”
Jeff McAffer, John Duimovich · ACM SIGPLAN OOPS Messenger · 1991
There have been several proposals for Concurrent Object-Oriented Programming Systems (COOPS) [Agha, Wegner and Yonezawa 89]. Unfortunately, most of these proposals are not powerful enough to be used outside the laboratory, that is, they are not industrial strength.
Cited by 2Open access
Piotr Nienaltowski · ETH Zürich Research Collection · 2007
Cited by 66Open access
Philipp Enrique Lim, Jr. · 1996
The development and maintenance of most real-time systems has always been problematic. In most real-time and embedded systems, software development usually employs ad-hoc methods, utilizing assembly or machine specific languages. Research on various algorithmic means for providing real-time program behaviour has been in existence since the 70's. Over the past two decades, real-time scheduling algorithms have gained tremendous popularity and maturity. However, a convenient means of utilizing such algorithms has lagged behind, given in part to the lack of a popular and flexible real-time programming language. Though various real-time programming languages exist, such languages usually offer little with regard to flexibility in controlling the underlying real-time scheduling algorithm. This thesis discusses the extension and transformation of a general purpose programming language into a flexible programming language suitable for real-time program development. iv Acknowledgements I wou...
Cited by 0
かおる 吉田 · Medical Entomology and Zoology · 1990
Cited by 2
Joana Campos, Vasco T. Vasconcelos · 2011
There is often a sort of a protocol associated to each class, stating when and how certain methods should be called. Given that this protocol is, if at all, described in the documentation accompanying the class, current mainstream object-oriented languages cannot provide for the verification of client code adherence against the sought class behaviour. We have defined a class-based concurrent objectoriented language that formalises such protocols in the form of usage types. Usage types are attached to class definitions, allowing for the specification of (1) the available methods, (2) the tests clients must perform on the result of methods, and (3) the object status — linear or shared — all of which depend on the object’s state. Our work extends the recent approach on modular session types by eliminating channel operations, and defining the method call as the single communication primitive in both sequential and concurrent settings. In contrast to previous works, we define a single category for objects, instead of distinct categories for linear and for shared objects, and let linear objects evolve into shared ones. We introduce a standard sync qualifier to prevent thread interference in certain operations on shared objects. We formalise the language syntax, the operational semantics, and a type system that enforces by static typing that methods are called only when available, and by a single client if so specified in the usage type. We illustrate the language via a complete example. 1
Cited by 0
C.-H. Jo · 1996
This paper discusses about the related issues occurring with adoption of concurrency and object-orientedness into a modular programming language, and presents new features for concurrent object-oriented programming. The base language of this work is CHILL, which is a high-level language for system programming recommended by CCITT(ITU-T). CHILL has been widely used by many telecommunication areas. Currently the effort to adopt object-oriented concepts into CHILL has been also actively done at ITU-T.
Cited by 2Open access
Katsumi Maruyama · Information Sciences · 1996
Cited by 1
Michael L. Nelson, Gilberto F. Mota, Vassilios Theologitis · ACM SIGAda Ada Letters · 1992
Although Ada supports concurrency and can thus be used as a concurrent programming language, it is not generally considered to be an object-oriented programming language. Classic-Ada is a preprocessor which adds the concepts of classes, inheritance, and dynamic binding to the Ada language. Classic-Ada is not billed as a concurrent object-oriented programming language, but it is possible to do anything in Classic-Ada that can be done in Ada. Thus, Classic-Ada can also serve as a concurrent object-oriented programming language. In this paper, we review the use of Classic-Ada in both concurrent and distributed environments.
Cited by 1Open access
Matthew Huntbach · 2007
Abstract This article introduces a concurrent object oriented language whose underlying operational semantics is based on the logic variable. The language is designed in reponse to Kahn’s criticisms [Kahn 89] of previous attempts to build concurrent object-oriented languages on top of concurrent logic languages. We believe Aldwych is a language which removes the verbosity of concurrent logic language code, without removing the power for abstract concurrent programming.
Cited by 0
Satoshi Matsuoka, Takuo Watanabe, Akinori Yonezawa · Lecture notes in computer science · 2006
Cited by 63
Satoshi Matsuoka, Akinori Yonezawa · The MIT Press eBooks · 1993
Cited by 119
Denis Caromel · ACM SIGPLAN Notices · 1988
This summary presents a general model supporting object-oriented programming in concurrent as well as distributed environments.The model combines the advantages of remote procedure calls with those of message passing.It relies on the following concepts:• All objects are not active but the active entities are objects.• Asynchronous Message Passing with Data-driven synchronization.• Service mechanism allowing an explicit thread of control.
Cited by 22Open access
Michael L. Nelson · ACM SIGPLAN Notices · 1994
Object-oriented programming (OOP) shows great potential for use in concurrent and distributed systems. However, several issues must be considered before moving into the concurrent/distributed arena. This paper considers the following issues: sharing of variables; various communication models; communication costs; and distributed object management.
Cited by 3
Svend Frølund · Lecture notes in computer science · 2006
Cited by 68
Denis Caromel · 1988
This summary presents a general model supporting object-oriented programming in concurrent as well as distributed environments.The model combines the advantages of remote procedure calls with those of message passing.It relies on the following concepts:• All objects are not active but the active entities are objects.• Asynchronous Message Passing with Data-driven synchronization.• Service mechanism allowing an explicit thread of control.
Cited by 7
松田裕幸, YUKO MATSUDA · Tokyo Tech Research Repository (Tokyo Institute of Technology) · 2006
Cited by 0
L. Kozma, T. Lakner · 2008
Studying concurrency one of the major difficulties is the need for a variety of programming languages to be available. But expecting students to learn at the same time a lot of languages is clearly undesirable. Concurrent object-oriented concepts can be understood more successfully if we have a programming language furnishing us with different kind of tools expressing concurrency and object-orientation at the same time. To achieve this aim an extension of Pascal-FC programming language is suggested for educational purposes. For the first step of extension a model of concurrent computation has to be selected. The candidates are Actor Model, Process Model of Objects, Alternative Models and Reflective Model of Objects. During next steps different kinds of synchronization schemes are included into the language to avoid inheritance anomalies. To increase the abstraction level of our programming language a scheme based on past-time propositional temporal logic will be implemented as well. The tools of implementation are based on Attribute Grammars. The programming language Pascal-FC Although constructs for concurrent programming vary from one language to another, three fundamental facilities must be present in one form or another in any concurrent programming language:- the expression of concurrent execution- inter-process synchronization- inter-process communication Three types of process behavior can be distinguished:- independent (this case is rare and essentially uninteresting for us)- competing (processes compete when the available system resources are in short supply. For example a multiuser operating system.)- co-operating ( The processes contained a concurrent program have common goal. Such processes therefore regularly communicate and synchronize activities in order to perform some common operations.) The programming language Pascal-FC (Functionally Concurrent) has been developed by A. Burns and G. Davies [1] as a teaching language that supports all the major primitives introduced in different kind of languages, for
Cited by 0
Konstantin Popov · 1995
In this paper I describe program development in Oz "by example" -- the Oz Browser [MMPS94]. The Oz Browser is a concurrent tool for displaying information about the values of variables. The Browser is a part of the Oz programming environment and is written in Oz itself. The Browser is a big and complex program (more than 15,000 lines of code). It exploits concurrency, objectoriented facilities and properties of the Oz execution strategy on a large scale. Development of the Browser can be seen as a "real-world" example and might give insights on suitable methodologies for development of Oz applications. This topic is not yet studied in papers dedicated to programming in Oz. Principles and techniques used in the Browser can also be applied to tasks like building interactive graphical applications, multi-agent and concurrent control systems. Keywords--- Oz, Application development, the Oz Browser, Concurrency, Object-Oriented Programming, the Oz Execution Strategy. 1. Introduction Oz [...
Cited by 0
Jun-ichiro Itoh, Yasuhiko Yokote · 1994
This paper proposes a new approach of implementing low-level OS components, especially device drivers. We introduce the notion of concurrent objects into device driver programming. A device driver for every hardware device is implemented as independent concurrent objects. A device driver object has a single thread of control, so that mutual exclusion operations such as spl and semaphores are not necessary. Mechanisms of synchronization, scheduling objects, and interrupt mask handling are clearly separated from actual device control programs, and these are implemented by the system for device driver objects. Both an interrupt and a service request to a device driver object will be delivered as a message, so programmers need not to distinguish these two types of invocation requests. Therefore, programmers can concentrate on writing the actual device control codes without writing auxiliary codes for synchronization, and the codes will be executed much safer. We show our implementation on ...
Cited by 4
松岡聡, Satoshi Matsuoka, 渡部 卓雄 et al. · Tokyo Tech Research Repository (Tokyo Institute of Technology) · 2006
Cited by 0