Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| people:etanter:taming-aspects [2013/04/18 16:46] – etanter | people:etanter:taming-aspects [2013/04/18 16:47] (current) – etanter | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Taming Aspects ====== | ||
| < | < | ||
| < | < | ||
| Line 15: | Line 14: | ||
| * {{bib> | * {{bib> | ||
| - | ---- | + | |
| + | ====== Taming Aspects ====== | ||
| **Abstract.** Aspect-oriented programming languages support the modular definition of crosscutting abstractions. In most languages, this is achieved through pointcuts, which provide a means for quantifying over execution events in order to implicitly trigger advice. Notably, an advice is more than a simple event handler because of its ability to override the underlying computation. Unrestricted quantification and arbitrary advice computation are powerful but dangerous. | **Abstract.** Aspect-oriented programming languages support the modular definition of crosscutting abstractions. In most languages, this is achieved through pointcuts, which provide a means for quantifying over execution events in order to implicitly trigger advice. Notably, an advice is more than a simple event handler because of its ability to override the underlying computation. Unrestricted quantification and arbitrary advice computation are powerful but dangerous. | ||
| In this talk we look at a number of approaches to tame aspects in order to retain their benefits without sacrificing important software engineering properties, like modular reasoning, separate development, | In this talk we look at a number of approaches to tame aspects in order to retain their benefits without sacrificing important software engineering properties, like modular reasoning, separate development, | ||