Aspect-Oriented Programming is Quantification and Obliviousness
By R. Filman, Daniel P. Friedman. 2000
718 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/175ed1427eb8ae425260fcc918e3fc616dafca19
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Christian Kästner
- Sven Apel
- Gunter Saake
- Gregor Kiczales
- Erik Hilsdale
- Thomas Thüm
- Mik Kersten
- Jim Hugunin
Citations in the corpus
- Implementing distribution and persistence aspects with aspectJ (2002, background): “In fact, the need for this kind of tool was reported elsewhere [7].”
- An Overview of AspectJ (2001, methodology): “If we add AOP to a procedural language, we must add constructs that crosscut the block structure of procedural programs [4, 6].”
- Feature-Oriented Software Product Lines (2013, background): “The most controversial concept of aspect-oriented programming is that the base program is oblivious with regard to the aspects that “hook into” the system (Filman and Friedman 2005).”