WG211/M3LawallLengauerDiscussion: Difference between revisions
m 1 revision |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Category:WG211]] | [[Category:WG211]] | ||
Julia Lawall and Christian Lengauer | |||
Title: | Title: | ||
| Line 45: | Line 39: | ||
<p> | <p> | ||
Position statements:<br> | Position statements:<br> | ||
Chris Lengauer: An algebra for AOP ([[ | Chris Lengauer: An algebra for AOP ([[Media:LengauerAOP.pdf | LengauerAOP.pdf]])<br> | ||
Julia Lawall: On pointcut languages ([[ | Julia Lawall: On pointcut languages ([[Media:dslides.pdf | dslides.pdf]])<br> | ||
Laurent Reveillere: AOP to simplify the implementation of a DSL ([[ | Laurent Reveillere: AOP to simplify the implementation of a DSL ([[Media:reveillere-aop.pdf | reveillere-aop.pdf]])<br> | ||
Ralf Lämmel: Report on "AOP goes .NET"<br> | Ralf Lämmel: Report on "AOP goes .NET"<br> | ||
Stephanie Weirich: Applications of AOP to security in AspectML ([[ | Stephanie Weirich: Applications of AOP to security in AspectML ([[Media:weirich-aop.ppt | weirich-aop.ppt]])<br> | ||
Todd Veldhuizen: Foozles: A retrospective ([[ | Todd Veldhuizen: Foozles: A retrospective ([[Media:foozles.pdf | foozles.pdf]]) | ||
Latest revision as of 14:39, 16 December 2011
Julia Lawall and Christian Lengauer
Title:
The Future and Potential of Aspect-Oriented Programming
Discussions Leaders: Julia Lawall and Christian Lengauer
Abstract:
Aspect orientation seems to be a fundamental paradigm
of software design, which is orthogonal to the paradigm
of modular programming. This session is meant to explore
what role aspect orientation can and should play in the
future of software design.
We pose the following questions for discussion:
- In what scenarios has aspect orientation proved to be
useful so far?
- tracing program executions
- program extension
- program optimization?
- what else?
- In what other scenarios can aspect orientation be useful in the future?
- How "general-purpose" is aspect orientation? Is it a general technique for program modification, or are there modifications it cannot or should not do?
- What should be a reference specification of aspect-oriented programming? AspectJ? A program algebra? Something else?
5-min position statements are invited. Please notify Julia or Chris if you are planning to give one.
Position statements:
Chris Lengauer: An algebra for AOP ( LengauerAOP.pdf)
Julia Lawall: On pointcut languages ( dslides.pdf)
Laurent Reveillere: AOP to simplify the implementation of a DSL ( reveillere-aop.pdf)
Ralf Lämmel: Report on "AOP goes .NET"
Stephanie Weirich: Applications of AOP to security in AspectML ( weirich-aop.ppt)
Todd Veldhuizen: Foozles: A retrospective ( foozles.pdf)
