Aspect-specification based on structural type information

Authors:
Stefan Hanenberg;Mohammed Al-Mansari;Rainer Unland
Affiliations:
University of Duisburg-Essen, Schützenbahn, Essen;University of Duisburg-Essen, Schützenbahn, Essen;University of Duisburg-Essen, Schützenbahn, Essen
Venue:
Proceedings of the 2006 ACM symposium on Applied computing
Year:
2006

Citing 11
Cited 1

Compound types for Java

Proceedings of the 13th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Refactoring: improving the design of existing code

Refactoring: improving the design of existing code
Types and programming languages

Types and programming languages
Arranging language features for more robust pattern-based crosscuts

Proceedings of the 2nd international conference on Aspect-oriented software development
Parametric introductions

Proceedings of the 2nd international conference on Aspect-oriented software development
Persistence as an aspect

Proceedings of the 2nd international conference on Aspect-oriented software development
An Overview of AspectJ

ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
AspectS - Aspect-Oriented Programming with Squeak

NODe '02 Revised Papers from the International Conference NetObjectDays on Objects, Components, Architectures, Services, and Applications for a Networked World
Advice weaving in AspectJ

Proceedings of the 3rd international conference on Aspect-oriented software development
AspectJ in Action: Practical Aspect-Oriented Programming

AspectJ in Action: Practical Aspect-Oriented Programming
Separation of concerns with procedures, annotations, advice and pointcuts

ECOOP'05 Proceedings of the 19th European conference on Object-Oriented Programming

Role annotations and adaptive aspect frameworks

Proceedings of the 3rd workshop on Linking aspect technology and evolution

Quantified Score

Hi-index	0.00

Visualization

Abstract

Aspects developed in aspect-oriented systems often need to hook onto multiple objects that share common structural characteristics - such as attributes and operations. In strongly-typed aspect-oriented systems like AspectJ these objects need to be of common type so that pointcuts may designate them and pieces of advice may interact with them. Such type-systems are typically based on nominal types, therefore, aspects cannot interact with objects according to their structural information in a common way. This paper argues that specifying aspects based on a nominal type system is not sufficient and shows that aspect-specifications based on structural characteristics overcome this problem. A corresponding extension of the nominal type systems is proposed and illustrated by means of structural types and compound types.