Implementing layered designs with mixin layers

Smaragdakis, Yannis; Batory, Don

doi:10.1007/bfb0054107

Cited by 166 publications

(107 citation statements)

References 30 publications

Supporting

Mentioning

106

Contrasting

Unclassified

Order By: Relevance

“…Other interesting extensions include supporting polymorphic types in the presence of separate typechecking and supporting module types and first-class modules to program mixin classes (Bracha and Cook, 1990;Flatt et al, 1998) and role-based programming (Reenskaug et al, 1992;VanHilst and Notkin, 1996;Smaragdakis and Batory, 1998). Finally, we are using the ideas in Dubious as a foundation for the design of Diesel, a practical programming language succeeding Cecil.…”

Section: Discussionmentioning

confidence: 99%

Modular Statically Typed Multimethods

Millstein

Chambers

1999

ECOOP’ 99 — Object-Oriented Programming

View full text Add to dashboard Cite

Multimethods offer several well-known advantages over the single dispatching of conventional object-oriented languages, including a simple solution to the binary method problem, a natural implementation of the strategy design pattern, and a form of open objects that enables easy addition of new operations to existing classes. However, previous work on statically typed multimethods whose arguments are treated symmetrically has required the whole program to be available in order to perform typechecking. We describe Dubious, a simple core language including first-class generic functions with symmetric multimethods, a classless object model, and modules that can be separately typechecked. We identify two sets of restrictions that ensure modular type safety for Dubious as well as an interesting intermediate point between these two. We have proved each of these modular type systems sound. C 2002 Elsevier Science (USA)

show abstract

Section: Discussionmentioning

confidence: 99%

Modular Statically Typed Multimethods

Millstein

Chambers

1999

ECOOP’ 99 — Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

“…Mixin layers [47] and extensions like aspectual mixin layers [4] are examples of language mechanisms typically used by such tools. Conceptually, mixin layers and aspectual mixin layers are quite close to our composition mechanisms, since our delegation-based model of composition has much of the same layering flavor.…”

Section: Related Workmentioning

confidence: 99%

Feature-Oriented Programming with Object Algebras

Oliveira

Storm

Loh

et al. 2013

ECOOP 2013 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. Object algebras are a new programming technique that enables a simple solution to basic extensibility and modularity issues in programming languages. While object algebras excel at defining modular features, the composition mechanisms for object algebras (and features) are still cumbersome and limited in expressiveness. In this paper we leverage two well-studied type system features, intersection types and type-constructor polymorphism, to provide object algebras with expressive and practical composition mechanisms. Intersection types are used for defining expressive run-time composition operators (combinators) that produce objects with multiple (feature) interfaces. Type-constructor polymorphism enables generic interfaces for the various object algebra combinators. Such generic interfaces can be used as a type-safe front end for a generic implementation of the combinators based on reflection. Additionally, we also provide a modular mechanism to allow different forms of self -references in the presence of delegation-based combinators. The result is an expressive, type-safe, dynamic, delegation-based composition technique for object algebras, implemented in Scala, which effectively enables a form of Feature-Oriented Programming using object algebras.

show abstract

“…A programming technique of mixin layers [27] supports collaboration-based design. A mixin layer is a set of mixins that is related to a collaboration.…”

Section: Applicationmentioning

confidence: 99%

“…Other than these, some studies have focused on collaborations instead of classes as units of reuse [11,31,27,14,22,23]. A collaboration is a set of the fields and methods of two or more classes in relation to a certain function.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Difference-Based Modules: A Class-Independent Module Mechanism

Ichisugi

Tanaka

2002

ECOOP 2002 — Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. We describe a module mechanism, which we call differencebased modules, and an object-oriented language we call MixJuice. MixJuice is an enhancement to the Java language that adopts difference-based modules instead of Java's original module mechanism. Modules are units of information hiding, reuse and separate compilation. We have completely separated the class mechanism and the module mechanism, and then unified the module mechanism and the differential programming mechanism. Although this module mechanism is simpler than that of Java, it enhances ease with which programs can be extended, reused and maintained. Collaborations that crosscut several classes can be separated into different modules. Modules are composable in the same way as mixins. The composition of modules sometimes causes name collision and an interesting phenomenon, which we call implementation defects. We describe solutions to these problems.

show abstract

Implementing layered designs with mixin layers

Cited by 166 publications

References 30 publications

Modular Statically Typed Multimethods

Modular Statically Typed Multimethods

Feature-Oriented Programming with Object Algebras

Difference-Based Modules: A Class-Independent Module Mechanism

Contact Info

Product

Resources

About