Introduction to AOP Aspect-Oriented Programming-basic concepts (3)

AOPIntroduction to Aspect-Oriented Programming----Basic concepts (3)

The Aspect-Oriented Programming idea is very simple. SlaveProcess-oriented and function-orientedProgrammingObject-orientedProgrammingInterface-orientedProgrammingComponents and modulesThe development history of programming we can know that the evolution of programming methodology expands the "boundary" of programming considerations step by step ". So far ourCosmic boundaries in the programming worldIt is a "class, interface, or component". In this boundary, we believe that one class can implement one interface dynamically, the behavior of existing classes is basically fixed before compilation. It is either a method defined inside the class, or a method inherited from the inheritance and implementation interfaces. However, in actual programming, we have encountered a "Cross-Boundary Situation", which requires multiple classes, interfaces, and components to work together, such as multi-thread concurrent access, centralized Control of program streams, serialization and program status maintenance, and the work that requires multiple "classes, interfaces, and component boundaries" to be completed. To better process multipleBoundaryAfter completing the same work, Aspect-Oriented Programming emerged. HereAspectTo complete the same task, we need to combine multiple classes, interfaces, and components for collaboration. You can think that the aspect is actually a larger class. This class is mainly composed of classes and interfaces in OOP. Of course, these classes and interfaces are so close that they act (methods) can be converted to each other. In fact, this is no big deal. Isn't the emergence of interfaces implementing dynamic changes to class behavior? Aspect-Oriented Programming is just an extension, which elevated the change to the interface level. Here, I feel: My ears are quiet, but the world is still not quiet, because it takes a long time to program with this idea, and support from more Tool developers.

In my subsequent articles, I want to unify the following concepts:
1. Inter-type declarations boundary internal type declaration: The Inter-type declaration has many forms in aspectj. It is used to describe the relationship between classes, the members and structure information of the classes.
2. Join point: the join point is a point defined in the program flow.
4. crosscutting concerns: consider border crossover
5. pointcuts connection point set: a set of states of multiple connection points held by the program running.
5. Advice notification point behavior: the connection point set is like a "structure" that contains multiple items and does not act itself. Its behavior is implemented by the notification point behavior.
The above terms are mainly used in the introduction of aspectj.

 

Accesine@163.com