Virtual classes: a powerful mechanism in object-oriented programming
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
OOPSLA/ECOOP '90 Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications
Subject-oriented programming: a critique of pure objects
OOPSLA '93 Proceedings of the eighth annual conference on Object-oriented programming systems, languages, and applications
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Programming in Ada95
Object-oriented programming in the BETA programming language
Object-oriented programming in the BETA programming language
ACM Transactions on Software Engineering and Methodology (TOSEM)
Reference Manual for the ADA Programming Language
Reference Manual for the ADA Programming Language
Conquering aspects with Caesar
Proceedings of the 2nd international conference on Aspect-oriented software development
J&: nested intersection for scalable software composition
Proceedings of the 21st annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications
Stateful traits and their formalization
Computer Languages, Systems and Structures
Transactions on Aspect-Oriented Software Development I
Challenges in the design of the package template mechanism
Transactions on Aspect-Oriented Software Development IX
Type-Safe symmetric composition of metamodels using templates
SAM'12 Proceedings of the 7th international conference on System Analysis and Modeling: theory and practice
Hi-index | 0.00 |
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.