Generic Universe Types

Abstract. This paper contributes a technique that expands the set of object invariants that one can reason about in modular verification. The technique uses history invariants, two-state invariants that describe the evolution of data values. The technique enables a flexible new way to specify and verify variations of the observer pattern, including iterators. The paper details history invariants and the new kind of object invariants, and proves a soundness theorem.

show abstract

“…The Boogie methodology lets a class declare a field with the rep modifier to say that the field references a rep object (cf. [8,6,7,25,10]). …”

Section: Boogie Methodologymentioning

confidence: 99%

Using History Invariants to Verify Observers

Leino

Schulte

2007

Programming Languages and Systems

View full text Add to dashboard Cite

show abstract

“…The basic idea of the box component model, namely to hierarchically structure the heap into dynamically created regions, originated from ownership disciplines. They were originally developed to check confinement properties by type systems (see [7] for an introduction and overview; [5] for a system to check concurrency properties; [10,22] for generic ownership type systems). Several different variants of ownership types exist, with varying expressiveness and flexibility.…”

Section: Conclusion Related and Future Workmentioning

confidence: 99%

“…This property does not allow for multiple objects at the boundary of a component. The Universe type system [16,10] is more flexible by permitting read-only references to owned objects. The ownership type system of Lu et al [15] generalize this by using an additional accessibility modifier.…”

Section: Conclusion Related and Future Workmentioning

confidence: 99%

A Calculus for Boxes and Traits in a Java-Like Setting

Bettini

Damiani

Luca

et al. 2010

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. The box model is a component model for the object-oriented paradigm, that defines components (the boxes) with clear encapsulation boundaries. Having well-defined boundaries is crucial in component-based software development, because it enables to argue about the interference and interaction between a component and its context. In general, boxes contain several objects and inner boxes, of which some are local to the box and cannot be accessed from other boxes and some can be accessible by other boxes. A trait is a set of methods divorced from any class hierarchy. Traits can be composed together to form classes or other traits. We present a calculus for boxes and traits. Traits are units of fine-grained reuse, whereas boxes can be seen as units of coarse-grained reuse. The calculus is equipped with an ownership type system and allows us to combine coarse-and fine-grained reuse of code by maintaining encapsulation of components.

show abstract

“…Both systems build on Java generics to check the additional properties. Peter Müller presented some of the ETH tools for Universe Types, namely the type checkers for Generic Universe Types (GUT) [14] and Universe Types with Transfer (UTT) [24]. Both Universe checkers are implemented in the compiler for the Java Modeling Language (JML) [20].…”

Section: Session 3: Concurrency and Ownership Demosmentioning

confidence: 99%

Aliasing, Confinement, and Ownership in Object-Oriented Programming

Clarke

Drossopoulou

Noble

2004

Object-Oriented Technology. ECOOP 2003 Workshop Reader

Self Cite

View full text Add to dashboard Cite

The power of objects lies in the flexibility of their interconnection structure. But this flexibility comes at a cost. Because an object can be modified via any alias, object-oriented programs are hard to understand, maintain, and analyze. Aliasing makes objects depend on their environment in unpredictable ways, breaking the encapsulation necessary for reliable software components, making it difficult to reason about and optimize programs, obscuring the flow of information between objects, and introducing security problems. Aliasing is a fundamental difficulty, but we accept its presence. Instead we seek techniques for describing, reasoning about, restricting, analyzing, and preventing the connections between objects and/or the flow of information between them. Promising approaches to these problems are based on ownership, confinement, information flow, sharing control, escape analysis, argument independence, read-only references, effects systems, and access control mechanisms.

show abstract

Generic Universe Types

Cited by 58 publications

References 12 publications

Using History Invariants to Verify Observers

Using History Invariants to Verify Observers

A Calculus for Boxes and Traits in a Java-Like Setting

Aliasing, Confinement, and Ownership in Object-Oriented Programming

Contact Info

Product

Resources

About