The following is purely personal understanding of the point of fur, a little understanding of the experience of the situation: \
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
AOP(Aspect Oriented Programming), Aspect Oriented Programming, Aspect Oriented Programming.
It’s not enough to have process orientation, object orientation, but also this aspect. What is it? Why do we have this thing?
The reason for the explanation of the data is that it is not enough to have object-oriented, like logging, exception handling, a lot of places to use, there are a lot of places to call the log package, exception handling package, things like that, the code is very fragmented.
AOP brings these calls together.
When I first started, I was wondering, didn’t we always do that? What’s so special about AOP in the process-oriented era, when we know we’re going to write a method or function out of repetitive code?
Originally, AOP and nothing out of a base class library for everybody to call such things, but like a database trigger mechanism, through independent set some trigger point (point), in the process of the program is running, the conditions are ripe namely triggers, and the program no longer write what call log statements such as, exception handling, package.
Thus, AOP is not a language like OPP(procedural oriented) or OOP (object-oriented), but rather a mechanism.
\
\
\
\
\
\