Depends on the context.
Just because a technique can cause fragility does not mean that the entire technique is worthless. For example, I still use inheritance when appropriate - despite the fragile base class problem - because the benefits outweigh the problems.
AOP can be a powerful technique. It has an upside and a downside. Sometimes the benefits outweigh the costs. Sometimes the costs outweigh the benefits.
For example, implementing logging or persistence via aspects can make your application a lot less fragile in the face of change. If you need to change your logging system or persistence layer you just need to alter a single aspect - rather than manually update thousands of methods.
Sometimes, especially in languages like Java, AOP is the best technique to pick.
In reply to Re^2: Aspect-Oriented Programming: Couple of Short Examples
by adrianh
in thread Aspect-Oriented Programming: Couple of Short Examples
by chunlou
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |