BibSonomy :: bibtex  ::

tag user group author concept BibTeX key search:all search:gron
A blue social bookmark and publication sharing system.
tags · relations · groups · popular
help · blog · about
login · register
gron's BibTeX entry:  

Aspect-Oriented Programming

ECOOP'97 — Object-Oriented Programming, : 220--242, 1997.
Authors: Gregor Kiczales and John Lamping and Anurag Mendhekar and Chris Maeda and Cristina Lopes and Jean-Marc Loingtier and John Irwin
URL: http://dx.doi.org/10.1007/BFb0053381
Description: SpringerLink - Buchkapitel
Tags: AOP Me:MastersThesis
Abstract: We have found many programming problems for which neither procedural nor object-oriented programming techniques are sufficient to clearly capture some of the important design decisions the program must implement. This forces the implementation of thosedesign decisions to be scattered throughout the code, resulting in “tangled” code that is excessively difficult to developand maintain. We present an analysis of why certain design decisions have been so difficult to clearly capture in actual code.We call the properties these decisions address aspects, and show that the reason they have been hard to capture is that they cross-cut the system's basic functionality. We present the basis for a new programming technique, called aspect-oriented programming,that makes it possible to clearly express programs involving such aspects, including appropriate isolation, composition andreuse of the aspect code. The discussion is rooted in systems we have built using aspect-oriented programming.
| URL | BibTeX  
@inproceedings{aop,
title = {Aspect-Oriented Programming},
author = {Gregor Kiczales and John Lamping and Anurag Mendhekar and Chris Maeda and Cristina Lopes and Jean-Marc Loingtier and John Irwin},
booktitle = {ECOOP'97 — Object-Oriented Programming},
pages = {220--242},
url = {http://dx.doi.org/10.1007/BFb0053381},
year = {1997},
description = {SpringerLink - Buchkapitel},
abstract = {We have found many programming problems for which neither procedural nor object-oriented programming techniques are sufficient to clearly capture some of the important design decisions the program must implement. This forces the implementation of thosedesign decisions to be scattered throughout the code, resulting in “tangled” code that is excessively difficult to developand maintain. We present an analysis of why certain design decisions have been so difficult to clearly capture in actual code.We call the properties these decisions address aspects, and show that the reason they have been hard to capture is that they cross-cut the system's basic functionality. We present the basis for a new programming technique, called aspect-oriented programming,that makes it possible to clearly express programs involving such aspects, including appropriate isolation, composition andreuse of the aspect code. The discussion is rooted in systems we have built using aspect-oriented programming.},
keywords = {AOP Me:MastersThesis }
}