From 34258fd0d72b707f2ef6a7b297608eaf01666e69 Mon Sep 17 00:00:00 2001 From: David Thompson Date: Wed, 5 Oct 2022 15:50:28 -0400 Subject: Fix mistakes in latest blog posts. --- posts/2022-10-05-goops-issues.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) (limited to 'posts/2022-10-05-goops-issues.md') 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 -- cgit v1.2.3