It also has daemon methods, which solve the problem of making sure the superclass gets to do something before, or after, the subclass method runs, without the subclass method having to request this explicitly.
(I love it when my attempt to RTFM is defeated by my being too stupid to find the FM in the first place ;)
The parent is probably talking about method combinations - in particular, the method combination used by default, which supports :before, :after and :around methods.
It's the first time I see the term "daemon method".
But the concept/term of a demon goes back to the end 60s to Hewitt's planner language and probably even earlier.
Later with generic functions in CLOS, I'd guess the term wasn't used, since something like an :after method is no longer conceptually a specific demon procedure attached to a slot via a facet, but a method in a method combination.
https://franz.com/support/documentation/8.1/doc/flavors.htm#...
> Great systems also have advice. There's no universally accepted name for this feature. Sometimes it's called hooks, or filters, or aspect-oriented programming. As far as I know, Lisp had it first, and it's called advice in Lisp. Advice is a mini-framework that provides before, around, and after hooks by which you can programmatically modify the behavior of some action or function call in the system. Not all advice systems are created equal. The more scope that is given to an advice system — that is, the more reach it has in the system it's advising — the more powerful the parent system will be.