Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Ive heard that AspectJ leads to modularity violations. Does it?

0
Posted

Ive heard that AspectJ leads to modularity violations. Does it?

0

Well I haven’t yet seen a language in which you can’t write bad code! But seriously, most AspectJ users find that just like when they learned OO, it takes a while to really get the hang of it. They tend to start in the usual way, by copying canonical examples and experimenting with variations on them. But users also find that rather than being dangerous, AspectJ helps them write code that is more clear and has better encapsulation — once they understand the kind of modularity AspectJ supports. There are several good papers that talk about this (see below), but here’s a basic point to keep in mind: when properly used, AspectJ makes it possible program in a modular way, something that would otherwise be spread throughout the code.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.