Ive heard that AspectJ leads to modularity violations. Does it?
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
- heard that some cities shorten the yellow-light cycle in order to increase the number of violations and increase revenue. Is that going to happen in Lewisville?
- I have heard the term short-form and long-form in connection with surveyd leads. What does this mean?
- Ive heard that AspectJ leads to modularity violations. Does it?
