Proceedings of the ACM SIGPLAN 2002 Conference on Programming Language Design and Implementation - PLDI '02 2002
DOI: 10.1145/512557.512559
|View full text |Cite
|
Sign up to set email alerts
|

Using data groups to specify and check side effects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
31
0

Year Published

2003
2003
2018
2018

Publication Types

Select...
5
4
1

Relationship

1
9

Authors

Journals

citations
Cited by 22 publications
(31 citation statements)
references
References 0 publications
0
31
0
Order By: Relevance
“…Finally, we note that ownership-based type systems have also been used for pre-venting data races [46] and deadlocks [43], for supporting modular software upgrades in persistent object stores [45], for modular specification of effects clauses in the presence of subtyping [44,46] (so they can be used as an alternative to data groups [144]), and for program understanding [13]. We are currently unifying the type system presented in this chapter with the above type systems [41].…”
Section: Resultsmentioning
confidence: 99%
“…Finally, we note that ownership-based type systems have also been used for pre-venting data races [46] and deadlocks [43], for supporting modular software upgrades in persistent object stores [45], for modular specification of effects clauses in the presence of subtyping [44,46] (so they can be used as an alternative to data groups [144]), and for program understanding [13]. We are currently unifying the type system presented in this chapter with the above type systems [41].…”
Section: Resultsmentioning
confidence: 99%
“…1 can modify Current.active but not Current.target). This construct enables fine-grained, yet abstract, frame specifications, in a way similar to data groups [LPZ02].…”
Section: Framingmentioning
confidence: 99%
“…In case x is null, this is well defined and designates the empty set of locations. We also allow f to be a data group [26], e.g., the built-in data group "any" that stands for all fields of an object.…”
Section: Effect Specifications and The Framing Of Commands And Formulasmentioning
confidence: 99%