I am stressing it to highlight the fallacy of
considering AOP a "programming paradigm".
AOP was not presented as 'a "programming paradigm"'. It serves as a novel example of "Generative Programming", which is the paradigm I mentioned.
The reasoning behind including AOP in the examples is based on the ability to use it to produce, manipulate, and/or otherwise enrich program flow independent of the assets being processed. Thus its "generative nature", such as when environments use declarative constructs (such as Java Annotations[0] or C# Attributes[1]) decorating functions/methods/types to manage DBMS transactions.
The reasoning behind including AOP in the examples is based on the ability to use it to produce, manipulate, and/or otherwise enrich program flow independent of the assets being processed. Thus its "generative nature", such as when environments use declarative constructs (such as Java Annotations[0] or C# Attributes[1]) decorating functions/methods/types to manage DBMS transactions.
0 - https://docs.oracle.com/javase/tutorial/java/annotations/bas...
1 - https://msdn.microsoft.com/en-us/library/aa288454(v=vs.71).a...