Challenges in the Design of the Package Template Mechanism

Axelsen, Eyvind W.; Sørensen, Fredrik; Krogdahl, Stein; Møller-Pedersen, Birger

doi:10.1007/978-3-642-35551-6_7

Cited by 6 publications

(8 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Basic PT [3,16] allows templates to have generic type parameters in much the same way as ordinary Java classes can, e.g. as in…”

Section: Required Type Specifications In Ptrmentioning

confidence: 99%

“…However, it is still important in some cases to be able to explicitly constrain a required type to be either an interface or a class. 3 As can be seen from the syntactical overview in Figure 1, such constraints can be imposed by declaring a required type explicitly as either a required interface or a required class. Declaring requirements in this way puts further constraints on the required types; e.g.…”

Section: Multiple Constraintsmentioning

confidence: 99%

“…With basic PT, classes (or interfaces) from different template instantiations can be merged to form one new class. The details of the merge mechanism are beyond the scope of this article, the interested reader is referred to [3] for a more thorough exposition.…”

Section: Template U { Inst T; Required Type R Adds Implements Runnablmentioning

confidence: 99%

“…The concepts of the mechanism are not in themselves tied to any particular object-oriented language, but the examples will be presented in a Javalike syntax. The interested reader is referred to [3,16] for a more thorough exposition.…”

Section: A Brief Overview Of the Basic Pt Mechanismmentioning

confidence: 99%

“…The mechanism is an extension of the Package Template (PT) mechanism [3,16]. We will in the following refer to the previously published variant as basic PT, or just PT when the variant is obvious from the context.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Adaptable generic programming with required type specifications and package templates

Axelsen

Krogdahl

2012

Proceedings of the 11th Annual International Conference on Aspect-Oriented Software Development

Self Cite

View full text Add to dashboard Cite

The aim of this work is to provide better support for adaption and refinement of generic code. This type of flexibility is desirable in order to fully reap the potential of generic programming. Our proposal for an improved mechanism is an extension to the previously published Package Templates (PT) mechanism, which is designed for development of reusable modules that can be adapted to their specific purpose when used in a program. The PT mechanism relies on compiletime specialization, and supports separate type checking and type-safe composition of modules. The extension to PT presented here is called required types, and can be seen as an enhanced form of type parameters, allowing them the same flexibility as other elements of the PT mechanism. We implement a subset of the Boost Graph Library in order to exemplify, validate, and compare our approach to other options.

show abstract

“…Basic PT [3,16] allows templates to have generic type parameters in much the same way as ordinary Java classes can, e.g. as in…”

Section: Required Type Specifications In Ptrmentioning

confidence: 99%

Section: Multiple Constraintsmentioning

confidence: 99%

Section: Template U { Inst T; Required Type R Adds Implements Runnablmentioning

confidence: 99%

Section: A Brief Overview Of the Basic Pt Mechanismmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%