Advocate of the devil time again:
Does anyone else but me feel that AOP and refactoring can be seen as opposite ends of a spectrum, and that one can be used to avoid the other?
Don't get me wrong, I appreciate AOP as valuable language mechanism in its own right, but quite a lot of examples of AOP I have seen seem just like avoiding refactoring, where the resulting code becomes unnecessary complex just to reach the holy grail of not having to touch existing code (which often can be very beneficical, but most of the time refactoring would be more future proof).
|