summaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
authorDavid Thompson <dthompson2@worcester.edu>2022-10-05 15:50:28 -0400
committerDavid Thompson <dthompson2@worcester.edu>2022-10-05 15:50:28 -0400
commit34258fd0d72b707f2ef6a7b297608eaf01666e69 (patch)
treece14b902343bb2e54c2eb75c26c3656e2fec4aa9 /posts
parentaa69a1248f2dec947c8f4c067d26fb13043b5fa9 (diff)
Fix mistakes in latest blog posts.
Diffstat (limited to 'posts')
-rw-r--r--posts/2022-10-05-goops-issues.md11
1 files changed, 1 insertions, 10 deletions
diff --git a/posts/2022-10-05-goops-issues.md b/posts/2022-10-05-goops-issues.md
index 2685279..b0e4266 100644
--- a/posts/2022-10-05-goops-issues.md
+++ b/posts/2022-10-05-goops-issues.md
@@ -170,7 +170,7 @@ without introducing backwards incompatible changes.
support these qualifiers and the method dispatching system could be
changed to accomodate them.
-## No controller over method combination algorithm
+## No control over method combination algorithm
This is related to the qualifier issue. Those before/after/around
qualifiers are part of the standard CLOS method combination algorithm.
@@ -308,15 +308,6 @@ generic could then be the union of its own documentation and any of
its methods that have documentation. There's probably a reason why
CLOS doesn't do this and it would be best to understand that first.
-## No control over method combination
-
-`defgeneric` in CLOS allows for customizing how methods are combined
-via the `:method-combination` option. GOOPS provides no such control,
-at least the documentation doesn't point out anything. There is a
-generic `add-method!` procedure but it's not clear to me if that could
-be hacked to change how methods are combined. Even if it could, it's
-a lot less pleasant than CLOS.
-
## Generics cannot be merged outside of a module
If I'm writing a Guile script, not a library module, I use