Aspectj in Action: Practical Aspect-Oriented Programming
By R. Laddad. 2003
549 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/820a1fd37839f4a65aa1ce160e3ec5e816e99670
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
- Martin Kuhlemann
- Erik Hilsdale
- Mira Mezini
- Don S. Batory
Citations in the corpus
- Aspect-oriented programming and modular reasoning (2005, background): “It has proven popular [15, 23, 26] because it makes it possible for developers to write modular code for concerns such as synchronization [11, 14], error handling [29], persistence [37], certain design patterns [18] etc.”
- Advice weaving in AspectJ (2004, background): “Advice Weaving in Aspectd Erik Hilsdale PARC 3333 Coyote Hill Rd Palo Alto, CA 94085 +1 650 812 4735 hilsdale @ parc.com Jim Hugunin Want of a Nail Software Sunnyvale, CA +1 650 812 4735 jim-aj@ hugunin.net ABSTRACT This paper describes the implementation of advice weaving in AspectJ.”
- Feature-Oriented Software Product Lines (2013, background): “Rather than explaining them, which is done elsewhere to a large extent (Laddad 2003), we illustrate the power by means of examples.”
- Granularity in software product lines (2008, methodology): “We could pass the parameter in a threadprotected field, use method objects (Fowler, 1999), use dummy or default parameters, employ AspectJ’s wormhole pattern (Laddad, 2003), or use parameter objects that encapsulate all parameters.”