Metaprogramming with Traits

Reppy, John; Turon, Aaron

doi:10.1007/978-3-540-73589-2_18

Cited by 34 publications

(61 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Traits were introduced and implemented in the dynamically-typed class-based language SQUEAK/SMALLTALK [11] 1 . Various formulations of traits in a JAVA-like setting can be found in the literature (see, e.g., [25,17,3,23,4,14]). Also two recent languages, SCALA and FORTRESS, incorporate forms of the trait construct.…”

Section: Introductionmentioning

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

Section: Introductionmentioning

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

show abstract

“…Namely, it is exploited to type trait functions, that provide a mechanism (termed trait-based metaproprograming) to obtain reusable class-member-level patterns. Another important difference between our proposal and the one in [24] is that, in the latter, traits play also the competing role of type, which instead we want to avoid.…”

Section: Conclusion Related and Further Workmentioning

confidence: 87%

“…We add here comparisons and remarks concerning the type system and the recent proposals on trait-based metaproprograming [24] and stateful traits [4].…”

Section: Conclusion Related and Further Workmentioning

confidence: 99%

“…Sophisticated hybrid nominal/structural type systems have been already proposed [11,19,24]. In particular, in [24], the combination of nominal and structural types is conceptually similar to ours, but exploited at a different level.…”

Section: Conclusion Related and Further Workmentioning

confidence: 99%

“…In particular, in [24], the combination of nominal and structural types is conceptually similar to ours, but exploited at a different level. Namely, it is exploited to type trait functions, that provide a mechanism (termed trait-based metaproprograming) to obtain reusable class-member-level patterns.…”

Section: Conclusion Related and Further Workmentioning

confidence: 99%

See 2 more Smart Citations

On Traits and Types in a Java-like Setting

Bono

Damiani

Giachino

Fifth Ifip International Conference on Theoretical Computer Science – TCS 2008

View full text Add to dashboard Cite

Both single and multiple class-based inheritance are often inappropriate as a reuse mechanism, because classes play two competing roles. Namely, a class is both a generator of instances and a unit of reuse. Traits are composable pure units of behavior reuse, consisting only of methods, that have been proposed as an add-on to single class-based inheritance in order to improve reuse. However, adopting traits as an add-on to traditional class-based inheritance is not enough: classes, besides their primary role of generators of instances, still play the competing role of units of reuse. Therefore, a style of programming oriented to reuse is not enforced by the language, but left to the programmer's skills. Traits have been originally proposed in the setting of dynamically typed language. When static typing is also taken into account, the role of unit of reuse and the role of type are competing, too.We argue that, in order to support the development of reusable program components, object oriented programming languages should be designed according to the principle that each software structuring construct must have exactly one role. We propose a realignment of the class-based object-oriented paradigm by presenting programming language features that separate completely the declarations of object type, behavior and generator. We illustrate our proposal through a core calculus and prove the soundness of the type system w.r.t. the operational semantics.

show abstract

Integrating Nominal and Structural Subtyping

Malayeri

Aldrich

ECOOP 2008 – Object-Oriented Programming

View full text Add to dashboard Cite

Metaprogramming with Traits

Cited by 34 publications

References 17 publications

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

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

On Traits and Types in a Java-like Setting

Integrating Nominal and Structural Subtyping

Contact Info

Product

Resources

About