What does aspect-oriented programming mean to Cobol?

Authors

Ralf Lämmel and Kris De Schutter

Abstract

We study AOP in the context of business programming with Cobol. We face the following questions: What are join points in Cobol programs? What is advice? Does classic Cobol provide any constructs that hint at AOP? (Yes!) What are typical crosscutting concerns in the Cobol world? How do otherwise typical crosscutting concerns make sense for Cobol? How does AOP for Cobol align with classic re-engineering transformations for Cobol? We deliver an AOP language design for Cobol. Codename: AspectCobol. While we adopt several ideas from AspectJ and friends, we also devise original techniques for join-point identification and context capture. We briefly discuss a prototypical implementation of AspectCobol.

Download

• Paper [.pdf]; [.ps]
• Slides [.ppt]; [.pdf]

Bibtex entry

@inproceedings{AspectCobol,
 author      = "R.~L{\"a}mmel and K.~{De Schutter}",
 title       = "{What does aspect-oriented programming mean to Cobol?}",
 booktitle   = "{Proceedings of Aspect-Oriented Software Development
                 (AOSD 2005)}",
 year        = 2005,
 month       = mar,
 publisher   = "ACM Press",
 note        = "12 pages"
}