Open Modules: Modular Reasoning about Advice

Aldrich, Jonathan

doi:10.21236/ada456038

Cited by 96 publications

(230 citation statements)

References 7 publications

Supporting

Mentioning

229

Contrasting

Unclassified

Order By: Relevance

“…While XPIs fix all pointcut interfaces beforehand, our conceptual model only fixes a classification of the structural source code entities. Another approach is presented by Aldrich in his work on Open Modules [22]. In this approach, modules must advertise which join points can be captured by the aspects that are external to the module.…”

Section: Discussionmentioning

confidence: 99%

Managing the Evolution of Aspect-Oriented Software with Model-Based Pointcuts

Kellens

Mens

Brichau

et al. 2006

ECOOP 2006 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. In spite of the more advanced modularisation mechanisms, aspect-oriented programs still suffer from evolution problems. Due to the fragile pointcut problem, seemingly safe modifications to the base code of an aspect-oriented program can have an unexpected impact on the semantics of the pointcuts defined in that program. This can lead to broken aspect functionality due to accidental join point misses and unintended join point captures. We tackle this problem by declaring pointcuts in terms of a conceptual model of the base program, rather than defining them directly in terms of how the base program is structured. As such, we achieve an effective decoupling of the pointcuts from the base program's structure. In addition, the conceptual model provides a means to verify where and why potential fragile pointcut conflicts occur, by imposing structural and semantic constraints on the conceptual model, that can be verified when the base program evolves. To validate our approach we implemented a model-based pointcut mechanism, which we used to define some aspects on SmallWiki, a medium-sized application, and subsequently detected and resolved occurrences of the fragile pointcut problem when this application evolved.

show abstract

Section: Discussionmentioning

confidence: 99%

Managing the Evolution of Aspect-Oriented Software with Model-Based Pointcuts

Kellens

Mens

Brichau

et al. 2006

ECOOP 2006 – Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

“…Evaluating program 1 2 returns a string representation " [1,2]" with both elements, whereas program 1 1 returns " [1]" with only one element. Indeed, both results are as expected.…”

Section: Open Function Applicationsmentioning

confidence: 99%

“…This section illustrates how we can exploit the monadic embedding of aspects to encode Open Modules [2] extended with effects. Additionally we present the notion of protected pointcuts, which are pointcuts whose type places restrictions on admissible advice.…”

Section: Open and Protected Modules With Effectsmentioning

confidence: 99%

Effective Aspects: A Typed Monadic Embedding of Pointcuts and Advice

Figueroa

Tabareau

Tanter

2014

Transactions on Aspect-Oriented Software Development XI

View full text Add to dashboard Cite

Abstract. Aspect-oriented programming (AOP) aims to enhance modularity and reusability in software systems by offering an abstraction mechanism to deal with crosscutting concerns. However, in most general-purpose aspect languages aspects have almost unrestricted power, eventually conflicting with these goals. In this work we present Effective Aspects: a novel approach to embed the pointcut/advice model of AOP in a statically-typed functional programming language like Haskell. Our work extends EffectiveAdvice, by Oliveira, Schrijvers and Cook; which lacks quantification, and explores how to exploit the monadic setting in the full pointcut/advice model. Type soundness is guaranteed by exploiting the underlying type system, in particular phantom types and a new anti-unification type class. Aspects are first-class, can be deployed dynamically, and the pointcut language is extensible, therefore combining the flexibility of dynamically-typed aspect languages with the guarantees of a static type system. Monads enables us to directly reason about computational effects both in aspects and base programs using traditional monadic techniques. Using this we extend Aldrich's notion of Open Modules with effects, and also with protected pointcut interfaces to external advising. These restrictions are enforced statically using the type system. Also, we adapt the techniques of EffectiveAdvice to reason about and enforce control flow properties. Moreover, we show how to control effect interference using the parametricity-based approach of EffectiveAdvice. However this approach falls short when dealing with interference between multiple aspects. We propose a different approach using monad views, a recently developed technique for handling the monad stack. Finally, we exploit the properties of our monadic weaver to enable the modular construction of new semantics for aspect scoping and weaving. These semantics also benefit fully from the monadic reasoning mechanisms present in the language. This work brings type-based reasoning about effects for the first time in the pointcut/advice model, in a framework that is both expressive and extensible; thus allowing development of robust aspect-oriented systems as well as being a useful research tool for experimenting with new aspect semantics.

show abstract

“…When Line.moveBy() is invoked, the advice is invoked three times: once for the call to Line.moveBy() and once for each call to Point.moveBy() in the body of Line.moveBy(). The assumption by the aspect about Line's otherwise-hidden implementation was broken by the apparently innocuous change [9].…”

Section: Data Member Accessmentioning

confidence: 99%

“…Open Modules expose only PCD-selected join points on private state [9]. The Open Modules system provides for the exposure of join points such that a module state that is intended to be hidden cannot be advised.…”

Section: Related Workmentioning

confidence: 99%