Conference Proceedings on Object-Oriented Programming Systems, Languages and Applications - OOPLSA '86 1986
DOI: 10.1145/28697.28722
|View full text |Cite
|
Sign up to set email alerts
|

Object-oriented concurrent programming ABCL/1

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
31
0
2

Year Published

1991
1991
2014
2014

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 199 publications
(33 citation statements)
references
References 0 publications
0
31
0
2
Order By: Relevance
“…What sets this model apart from most other actor languages (such as Act1 [30], ABCL [18], Actalk [31], Salsa [32], Erlang [8], Kilim [33], ProActive [34] or Scala actors [35]), is that:…”
Section: Communicating Event Loopsmentioning
confidence: 99%
See 1 more Smart Citation
“…What sets this model apart from most other actor languages (such as Act1 [30], ABCL [18], Actalk [31], Salsa [32], Erlang [8], Kilim [33], ProActive [34] or Scala actors [35]), is that:…”
Section: Communicating Event Loopsmentioning
confidence: 99%
“…The use of futures as return values from asynchronous message sends can be traced back to actor languages such as ABCL/1 [18]. In Argus, promises additionally supported pipelined message sends and exceptions [20].…”
Section: Related Workmentioning
confidence: 99%
“…In concurrent object-oriented programming languages, futures have been a recurring language abstraction to reconcile asynchronous message passing with return values (e.g. future-type message passing in ABCL [15] or promises in Argus [16] and E [17]). A future is essentially a handle for the result of an asynchronous message send.…”
Section: Futuresmentioning
confidence: 99%
“…Rather than employing a multithreaded concurrency model, AmbientTalk's model is founded on the actor model of computation [20] and its many incarnations in languages such as Act1 [21], ABCL [15] and Actalk [22]. However, AmbientTalk's closest relative is the E programming language [17] (further described in Section 9.2).…”
Section: Ambienttalkmentioning
confidence: 99%
“…They serve as an essential synchronisation tool when asynchronous message passing semantics are introduced. The use of futures as return values from asynchronous message sends can be traced back to actor-based languages such as ABCL [18]. In Argus, futures were further extended to support pipelined message sends [24].…”
Section: Related Workmentioning
confidence: 99%