Programming languages and environments that support AOP lack expressive power to manage the interference between components and aspects. We illustrate this problem in an example and identify the needed expressive power. We propose aspect integration contracts to fill the gap. These contracts specify the permitted interference between an aspect and a base component. We discuss the impact of our observations on language design, and the impact of a solution on software engineering properties.
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.