aboutsummaryrefslogtreecommitdiff
path: root/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.md
diff options
context:
space:
mode:
Diffstat (limited to '_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.md')
-rw-r--r--_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.md b/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.md
index eb19b38..cce0e42 100644
--- a/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.md
+++ b/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.md
@@ -131,3 +131,7 @@ But when defining a generic function, the order of arguments is more important t
One shouldn't change the order of arguments of a generic function for the sake of tailoring it to the CLOS priority ranking algorithm, but doing it for a class definition is just fine.
TIL.
+
+## References
+
+1. [Object-Oriented Programming in Common Lisp: A Programmer's Guide to CLOS](https://en.wikipedia.org/wiki/Object-Oriented_Programming_in_Common_Lisp), by Sonja E. Keene