User loginNavigation |
A fresh look at AOP - Use classes to define behavior, use aspects to compose behaviorA fresh look at AOP, by Carlo Pescio (http://www.aspectroid.com) "Aspectroid is an exploration of the design space, moving beyond conventional object oriented design and further into the aspect-oriented expanse. [...] to best combine OOP and AOP, [...] AOP is a powerful, yet largely misunderstood and misrepresented paradigm." "I started this project with a design vision in my mind, and a set of hypothesis that I wanted to test. My vision was to use aspects to improve object-oriented design, or more exactly statically-typed object-oriented design, so that I could have the benefits of static typing, but also enjoy the flexibility usually associated with dynamic languages like Smalltalk. Actually, I wanted to move one step forward, and aim for a degree of compositionality beyond what is normally possible with OOP alone. Behind that vision, I had a few, relatively straightforward goals: - Align the architecture with the nature of the problem [...] "AOP goals: Use aspects to separate application concerns, as opposed to what we commonly see in literature, where technological concerns like logging, exception handling, etc. are usually addressed." By M Riccobene at 2014-08-22 11:33 | LtU Forum | previous forum topic | next forum topic | other blogs | 3785 reads
|
Browse archives
Active forum topics |
Recent comments
22 weeks 6 days ago
22 weeks 6 days ago
22 weeks 6 days ago
45 weeks 1 day ago
49 weeks 3 days ago
51 weeks 6 hours ago
51 weeks 6 hours ago
1 year 1 week ago
1 year 6 weeks ago
1 year 6 weeks ago