2012
DOI: 10.1016/j.jlap.2012.03.009
|View full text |Cite
|
Sign up to set email alerts
|

Termination detection for active objects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
4
0

Year Published

2012
2012
2015
2015

Publication Types

Select...
2
2
1

Relationship

1
4

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 9 publications
0
4
0
Order By: Relevance
“…We argue that our technique outperforms previous proposals [8,5,4,7] in precision or efficiency and it considers a more expressive language. Experiments suggest we achieve better precision than [8,7] because our pointsto analysis keeps a more fine-grained representation of objects and their dependencies than their contract-based approach.…”
Section: Related Work and Conclusionmentioning
confidence: 74%
See 1 more Smart Citation
“…We argue that our technique outperforms previous proposals [8,5,4,7] in precision or efficiency and it considers a more expressive language. Experiments suggest we achieve better precision than [8,7] because our pointsto analysis keeps a more fine-grained representation of objects and their dependencies than their contract-based approach.…”
Section: Related Work and Conclusionmentioning
confidence: 74%
“…6. The language used in [5] is very restrictive (e.g., it does not have an object creation instruction, nor synchronizations using await, among other limitations). More recent work [4] improves the previous one, since the use of Petri nets specifies the temporal behavior of the methods.…”
Section: Related Work and Conclusionmentioning
confidence: 99%
“…Actors form a well established model for distributed systems [YBS86,Ame89,Car93,SPH10], which is lately regarding attention due to its adoption in Erlang [AVW96], Scala [HO09] and active objects [SPH10,BGS12]. In our language, the distribution model is based on (possibly interacting) objects that are grouped into distributed nodes, called coboxes.…”
Section: Introductionmentioning
confidence: 99%
“…Recent work on actor-based language focusses on deadlock analysis: In [18], a technique for the deadlock analysis has been introduced for a version of Featherweight Java which features asynchronous method invocations and a synchronization mechanism based on futures variables. The approach followed in [15] for detecting deadlock in an actor-like subset of Creol [7] is based on suitable over-approximations.…”
Section: Introductionmentioning
confidence: 99%