2005
DOI: 10.1007/11561163_12
|View full text |Cite
|
Sign up to set email alerts
|

A Dynamic Binding Strategy for Multiple Inheritance and Asynchronously Communicating Objects

Abstract: This paper considers an integration of asynchronous communication, virtual binding, and multiple inheritance. Object orientation is the leading paradigm for concurrent and distributed systems, but the tightly synchronized RPC communication model seems unsatisfactory in the distributed setting. Asynchronous messages are better suited, but lack the structure and discipline of traditional object-oriented methods. The integration of messages in the object-oriented paradigm is unsettled, especially with respect to … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2006
2006
2011
2011

Publication Types

Select...
2
2

Relationship

3
1

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 39 publications
0
5
0
Order By: Relevance
“…We say that a call to a method m is bound with respect to a search class D; i.e., bind(D, m) denotes the search for a definition of m which starts in D. In this case, the call must bind to a definition of m in a class above D, such that no other definition of m is found by the search below this class. Following [10,13,22] where D.inh D reduces to D when D.inh is empty. Observe that this strategy is not healthy, since an internal call would be bound independently of where the call-site occurs in the class hierarchy, i.e., the class in which the call textually occurs.…”
Section: The Binding Of Methods Calls and Fieldsmentioning
confidence: 99%
See 1 more Smart Citation
“…We say that a call to a method m is bound with respect to a search class D; i.e., bind(D, m) denotes the search for a definition of m which starts in D. In this case, the call must bind to a definition of m in a class above D, such that no other definition of m is found by the search below this class. Following [10,13,22] where D.inh D reduces to D when D.inh is empty. Observe that this strategy is not healthy, since an internal call would be bound independently of where the call-site occurs in the class hierarchy, i.e., the class in which the call textually occurs.…”
Section: The Binding Of Methods Calls and Fieldsmentioning
confidence: 99%
“…This may be due to the complexity of resolving method binding, as discussed in Section 2, which may easily cause ambiguities. However, multiple inheritance is supported in, e.g., C++ [38], CLOS [13], Eiffel [29], Ocaml [26], POOL [2], Self [10], and Creol [22]. Horizontal name conflicts in C++, POOL, and Eiffel are removed by explicit resolution, after which the inheritance graph may be linearized.…”
Section: Related Workmentioning
confidence: 99%
“…3 Creol: A Language for Distributed Concurrent Objects Creol is a high-level object-oriented language targeting open distributed systems by combining interface types and concurrent objects with asynchronous method calls, and by combining active and reactive object behavior [13,15]. In this paper blocking and nonblocking (suspending) method calls are considered, although the results of the paper apply to the full language.…”
Section: Behavioral Interfacesmentioning
confidence: 99%
“…The class identifier for version n of class C is denoted C#n. The rules for the static language constructs may be found in [13]. Focus here is on method binding and dynamic class constructs, given in Figure 5.…”
Section: Operational Semanticsmentioning
confidence: 99%
See 1 more Smart Citation