we already have fairly
good techniques for separating aspects
of programs, and we don�t use them
I do however agree with the fact that it is not easy to identify the aspects present in a system and also that we don't know exactly when it is good to separate them.
Why did a whole bunch of people recognize the need for developing new techniques for separating "aspects" and created a whole community on Aspect-Oriented Software Development (AOSD)?
Originally posted by Bhushan Jawle:
AspectWerkz is another framework for AOP. I am a bit confused by your 1st question though. Does a language need to support AOP ?
AspectJ is an aspect-oriented programming language (that uses Java as the base language), much like Java is an object-oriented programming language.
Please note that the statement quoted in Martin's article comes from Ralph Johnson which does not imply that Martin is against AOP!
Whoever has managed to gather proven AOP patterns and repeatable steps to follow... and who has enough balls to write a sequel for "The Bible."
Who'll be rewriting the refactoring book ?
Don't worry, Refactoring will be Good Stuff for years to come
And I've just bought that.
I will invite Ralph Johnson and Martin Fowler to participate in this discussion