aboutsummaryrefslogtreecommitdiff
path: root/_tils
diff options
context:
space:
mode:
Diffstat (limited to '_tils')
-rw-r--r--_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.md2
-rw-r--r--_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.md4
2 files changed, 5 insertions, 1 deletions
diff --git a/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.md b/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.md
index 7965d29..d06f0c1 100644
--- a/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.md
+++ b/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.md
@@ -77,7 +77,7 @@ After any of those checkouts, you have to `git reset .` to reset your current
staging area back to what it was before the checkout.
-## References:
+## References
1. [GIT: Checkout to a specific folder][0] (StackOverflow)
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