AOP use cases

[John J. Lee]

"John Roth" <newsgroups at jhrothjr.com> writes:
[...]
> When you're supporting a monolithic proprietary application,
> sometimes you have to do what you have to do, but today
> the entire idea simply smells of a high-tech way to do
> ad-hoc patching where a really well designed application
> would not need it (and I don't really care if the design is
> up front or emergent.)

That's unfair.

Regardless of your view of its importance, AOP is clearly sufficiently
well-motivated purely in terms of separation of concerns.  That it's
also useful as a hack to patch badly-designed software written in
inflexible languages doesn't change that in the least.


John