Modular Specification of Encapsulated Object-Oriented Components

Poetzsch-Heffter, Arnd; Schäfer, Jan

doi:10.1007/11804192_15

Cited by 12 publications

(10 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We exploited this information in the context of distributed object-oriented programming to check whether an access or method call is local or remote. Locations can also be used for other purposes, in particular -as scheduling units in multi-core scenarios [23], -to raise the level of granularity of memory management and garbage collection from single objects to group of objects [24], -for encapsulation of objects [25] or other values [13], and -to support specification and verification techniques [26].…”

Section: Discussion and Related Workmentioning

confidence: 99%

Location Types for Safe Programming with Near and Far References

Welsch

Schäfer

Poetzsch-Heffter

2013

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. In distributed object-oriented systems, objects belong to different locations. For example, in Java Remote Method Invocation (RMI), objects can be distributed over different Java virtual machines. Accessing a reference in RMI has crucially different semantics depending on whether the referred object is local or remote. Nevertheless, such references are not statically distinguished by the Java type system. This chapter presents location types, which statically distinguish far from near references. We present a formal type system for a minimal core language and develop a type inference system that gives maximally precise solutions satisfying further desirable properties. We prove soundness of the type system as well as soundness and correctness of the inference system. We have implemented location types as a pluggable type system for the ABS language, an object-oriented language with a concurrency and distribution model based on concurrent object groups. To facilitate programming with location types, we provide a tight integration of the type and inference system with an Eclipse-based integrated development environment (IDE) that presents inference results as overlays to the source code. The IDE drastically reduces the annotation overhead while providing full static type information to the programmer.

show abstract

Section: Discussion and Related Workmentioning

confidence: 99%

Location Types for Safe Programming with Near and Far References

Welsch

Schäfer

Poetzsch-Heffter

2013

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…During runtime each object belongs to exactly one box, thus defining a clear runtime boundary. A more detailed description including the discussion of design decisions and showing the use of the model for modular specification can be found in [20].…”

Section: Motivating Examplementioning

confidence: 99%

“…The cast restriction allows the implementation to be changed without breaking compatibility with clients, even in the presence of downcasting. This also improves the reasoning about the behavior and about properties of a box in a modular way (see [20] for more details). Figure 3 shows an example client implementation.…”

Section: Motivating Examplementioning

confidence: 99%

“…In practice, however, objects often rely on other objects to hold additional state and realize additional behavior, forming implicit components at runtime. The box model [20,19,21] is a component model, which makes these components explicit. It defines components both on a syntactic level (by a set of classes) and as a runtime entity (as a set of objects).…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

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

Bettini

Damiani

Luca

et al. 2010

Lecture Notes in Computer Science

Self Cite

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

“…Boxes [36] is an alias control schema based on ownership types. The system requires that the program is split into a series of modules, each of which is similar to alias-protected containers [32].…”

Section: Boxes Inferencementioning

confidence: 99%

OwnKit: Ownership Inference for Java

Dymnikov¹

View full text Add to dashboard Cite

<p>Object ownership allows us to statically control run-time aliasing in order to provide a strong notion of object encapsulation. Unfortunately in order to use ownership, code must first be annotated with extra type information. This imposes a heavy burden on the programmer, and has contributed to the slow adoption of ownership. Ownership inference is the process of reconstructing ownership type information based on the existing ownership patterns in code. This thesis presents OwnKit—an automatic ownership inference tool for Java. OwnKit conducts inference in a modular way: by only considering a single class at the time. The modularity makes our algorithm highly scalable in both time and memory usage.</p>

show abstract

Modular Specification of Encapsulated Object-Oriented Components

Cited by 12 publications

References 21 publications

Location Types for Safe Programming with Near and Far References

Location Types for Safe Programming with Near and Far References

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

OwnKit: Ownership Inference for Java

Contact Info

Product

Resources

About