The Greybox Approach: When Blackbox Specifications Hide Too Much
The Greybox Approach: When Blackbox Specifications Hide Too Much
A classification system and analysis for aspect-oriented programs
Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering
Aspect-oriented programming and modular reasoning
Proceedings of the 27th international conference on Software engineering
Bridging Java and AspectJ through explicit join points
Proceedings of the 5th international symposium on Principles and practice of programming in Java
Modular verification of higher-order methods with mandatory calls specified by model programs
Proceedings of the 22nd annual ACM SIGPLAN conference on Object-oriented programming systems and applications
Ptolemy: A Language with Quantified, Typed Events
ECOOP '08 Proceedings of the 22nd European conference on Object-Oriented Programming
Modular aspect-oriented design with XPIs
ACM Transactions on Software Engineering and Methodology (TOSEM)
Open modules: modular reasoning about advice
ECOOP'05 Proceedings of the 19th European conference on Object-Oriented Programming
| Hi-index | 0.00 |
Making assertions about the program's control flow is important for reasoning purposes, e.g. ensuring that an advice proceeds to the original join point. Obliviousness of the base modules to the aspects in aspect oriented languages, like AspectJ, makes it difficult to make such assertions in a modular manner. Base-aspect interfaces like crosscutting interfaces (XPIs), augmented with blackbox behavioral contracts save modularity of the reasoning process to some extent, but are not expressive enough to specify base-aspect control interactions in their full generality. Translucid contracts are proposed to specify and enforce typical control flow properties.