Exploring the use of Package Templates for flexible re-use of Collections of related Classes.

Krogdahl, Stein; Møller-Pedersen, Birger; Sørensen, Fredrik

doi:10.5381/jot.2009.8.7.a1

Cited by 18 publications

(22 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As in package templates [KMPS09], we choose a more radical approach, that is, subclassing and subtyping are totally unrelated and the latter should be explicitly declared by the programmer (as explained at page 7), hence in the example there is no a priori subtyping relation between A and AA.…”

Section: Discussion and Related Workmentioning

confidence: 99%

“…More advanced mechanisms are provided by package templates [KMPS09], which are collections of classes. However, differently from standard Java packages where an import clause only provides a shorter name for a class which is in any case part of the current class table, here importing a package template has the effect of adding its classes, either as they stand or with some modification, to the class table, by a precompilation step analogous to our flattening.…”

Section: Jigsaw-like Operatorsmentioning

confidence: 99%

See 1 more Smart Citation

DeepFJig — Modular composition of nested classes.

Corradi¹,

Servetto²,

Zucca³

2012

JOT

View full text Add to dashboard Cite

We present a new language design which smoothly integrates modular composition and nesting of Java-like classes. That is, inheritance has been replaced by an expressive set of composition operators, inspired by Bracha's Jigsaw framework, and these operators allow to manipulate (e.g., rename or duplicate) a nested class at any level of depth. Typing is nominal as characteristic of Java-like languages, so types are paths of the form outer n .C 1 . . . . .C k which, depending on the class (node) where they occur, denote another node in the nesting tree. However, paths denoting the same class are not equivalent, since they behave differently w.r.t. composition operators.The resulting language, called DEEPFJIG, obtains a great expressive power, allowing, e.g., to solve the expression problem, encode basic AOP mechanisms, and bring some refactoring techniques at the language level, while keeping a very simple semantics and type system which represent a natural extension for, say, a Java programmer.

show abstract

Section: Discussion and Related Workmentioning

confidence: 99%

Section: Jigsaw-like Operatorsmentioning

confidence: 99%

DeepFJig — Modular composition of nested classes.

Corradi¹,

Servetto²,

Zucca³

2012

JOT

View full text Add to dashboard Cite

show abstract

“…Package Templates [12], or PT for short, is another such mechanism, and it is especially aimed at supporting code reusability. A template is a kind of package (that is, a set of classes called template classes), but it must be instantiated as part of a program before the template classes become ordinary classes in the program, and such instantiations are done at compile time.…”

Section: Introductionmentioning

confidence: 99%

Reuse and combination with package templates

Sørensen

Axelsen

Krogdahl

2010

Proceedings of the 4th Workshop on MechAnisms for SPEcialization, Generalization and inHerItance

Self Cite

View full text Add to dashboard Cite

Package Templates (PT) is a mechanism for writing modules meant for reuse, where each module (template) consists of a collection of classes. Such a template must be instantiated in a program (at compile time) to form a set of ordinary classes, and during instantiation the classes may be adjusted with renaming and additional attributes. Package templates can be instantiated multiple times in the same program, each time with different adjustments and each time resulting in a fully independent set of classes. During instantiations, classes from two or more templates may be combined so that they get a new shared type with the properties from all the classes. This paper presents and discusses two proposed extensions to PT. The first has to do with the fact that PT naturally gets two variants of the "super" concept, where one is for ordinary superclasses, and the other is for the additions made to classes during instantiation. The second extension has to do with allowing templates to instantiate templates that are later to be specified.

show abstract

“…To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. The package template (PT) mechanism [9,10,17] targets the development of collections of reusable interdependent classes. Such a collection is a template for a package, that may be instantiated at compile time, thus forming an ordinary package.…”

Section: Introductionmentioning

confidence: 99%