Aspect-oriented programming: Difference between revisions

Content deleted Content added
Line 86:
One can think of AOP as a debugging tool or as a user-level tool. Advice should be reserved for the cases where you cannot get the function changed (user level)<ref>{{cite web|url=https://www.gnu.org/software/emacs/manual/html_node/elisp/Advising-Functions.html|title=gnu.org|author=|date=|website=www.gnu.org|accessdate=5 May 2018|deadurl=no|archiveurl=https://web.archive.org/web/20171224053656/http://www.gnu.org/software/emacs/manual/html_node/elisp/Advising-Functions.html|archivedate=24 December 2017|df=}}</ref> or do not want to change the function in production code (debugging).
 
==Join point models==> adfasfs
The advice-related component of an aspect-oriented language defines a join point model (JPM). A JPM defines three things: