Mixin modules

Duggan, Dominic; Sourelis, Constantinos

doi:10.1145/232629.232654

Cited by 21 publications

(25 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Scala's design of mixins comes from object-oriented linear mixins [3], but defines mixin composition in a symmetric way, similar to what is found in mixin modules [8,18] or traits [41]. Jiazzi [30] is an extension of Java that adds a module mechanism based on units [15], a powerful form of parametrized modules.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Scalable component abstractions

Odersky

Zenger

2005

Proceedings of the 20th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications

149

View full text Add to dashboard Cite

We identify three programming language abstractions for the construction of reusable components: abstract type members, explicit selftypes, and modular mixin composition. Together, these abstractions enable us to transform an arbitrary assembly of static program parts with hard references between them into a system of reusable components. The transformation maintains the structure of the original system. We demonstrate this approach in two case studies, a subject/observer framework and a compiler front-end.

show abstract

Section: Related Workmentioning

confidence: 99%

“…Mixin class composition in Scala is a fusion of the objectoriented, linear mixin composition of Bracha [3], and the more symmetric approaches of mixin modules [8,18] and traits [41]. To start with an example, consider the following abstraction for iterators.…”

Section: Modular Mixin Compositionmentioning

confidence: 99%

Scalable component abstractions

Odersky

Zenger

2005

Proceedings of the 20th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications

149

View full text Add to dashboard Cite

show abstract

“…His mixins do not address the initialization issue. Duggan and Sourelis [10] extended his proposal and adapted it to ML. In their system, a mixin comprises a body, containing only function and data-type definitions, surrounded by a prelude and an initialization section, containing arbitrary computations.…”

Section: Related Workmentioning

confidence: 99%

Call-by-Value Mixin Modules

Hirschowitz

Leroy

Wells³

2004

Programming Languages and Systems

View full text Add to dashboard Cite

show abstract

“…Most typed object-oriented languages provide object polymorphism a few o er parametric polymorphism. 6 Pizza's parametric polymorphism greatly facilitates the implementation of Extensible Visitors. 7 To illustrate this point in more detail, we c o n trast the Pizza implementation with one in Java.…”

Section: Typesmentioning

confidence: 99%

Synthesizing object-oriented and functional design to promote re-use

Krishnamurthi

Felleisen

Friedman

1998

ECOOP’98 — Object-Oriented Programming

View full text Add to dashboard Cite

Many problems require recursively speci ed types of data and a collection of tools that operate on those data. Over time, these problems evolve so that the programmer must extend the toolkit or extend the types and adjust the existing tools accordingly. Ideally, this should be done without modifying existing code. Unfortunately, the prevailing program design strategies do not support both forms of extensibility: functional programming accommodates the addition of tools, while object-oriented programming supports either adding new tools or extending the data set, but not both. In this paper, we present a composite design pattern that synthesizes the best of both approaches and in the process resolves the tension between the two design strategies. We a l s o show h o w this protocol suggests a new set of linguistic facilities for languages that support class systems. Evolutionary Software DevelopmentProgramming practice frequently confronts programmers with the following design dilemma. A recursively de ned set of data must be processed by s e v eral di erent tools. In anticipation of future extensions, the data speci cation and the tools should therefore be implemented such that it is easy to 1. add a new variant of data and adjust the existing tools accordingly, a n d 2. extend the collection of tools. Ideally, these extensions should not require any c hanges to existing code. For one, source modi cation is cumbersome and error-prone. Second, the source may not be available for modi cation because the tools are distributed in the form of object code. Finally, i t m a y be necessary to evolve t h e b a s e This dilemma manifests itself in many di erent application areas. A particularly important example arises in the area of programming languages. Language grammars are typically speci ed via BNFs, which denote recursively de ned data sets. Language-processing tools recursively traverse sentences formed from the grammar. In this scenario, a new form of data means an additional clause in the BNF new tools must be able to traverse all possible elements of the (extended) grammar.Unfortunately, p r e v ailing design strategies do not accommodate the required evolution:The \functional" approach, which is often realized with conventional procedural languages, implements tools as procedures on recursive t ypes. While this strategy easily accommodates the extension of the set of tools, it requires signi cant source modi cations when the data set needs to be extended. The (standard) \object-oriented" approach de nes a recursive set of data with a collection of classes, one per variant (BNF clause), and places one method per tool in each c l a s s . I n the parlance of object-oriented design patterns 13], this approach i s k n o wn as the Interpreter pattern. The problem it poses is dual to the problem of the functional approach: variants are easy to add, while tool additions require code modi cations. If the collection of tools is large, the designer may also use the Visitor pattern, a variant o f t h e Interpreter...

show abstract

Mixin modules

Cited by 21 publications

References 19 publications

Scalable component abstractions

Scalable component abstractions

Call-by-Value Mixin Modules

Synthesizing object-oriented and functional design to promote re-use

Contact Info

Product

Resources

About