From 6381de5914df79b2c807c518e9aa04e20125d643 Mon Sep 17 00:00:00 2001 From: David Thompson Date: Tue, 27 Dec 2022 19:40:45 -0500 Subject: Fix GOOPS post. Thanks to mfiano on IRC for pointing out the error. --- posts/2022-10-05-goops-issues.md | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) (limited to 'posts') diff --git a/posts/2022-10-05-goops-issues.md b/posts/2022-10-05-goops-issues.md index b0e4266..d4eab3e 100644 --- a/posts/2022-10-05-goops-issues.md +++ b/posts/2022-10-05-goops-issues.md @@ -296,17 +296,8 @@ documentation for a generic. One complicating factor is that `generic-function-name` and `generic-function-methods` are defined in libguile, which is C, not Scheme. I don't know if this hypothetical `generic-function-documentation` would have to be in C, too. - -In CLOS, methods do not accept documentation strings, only generics -do. The downside of doing the same is that most code using GOOPS that -I've seen does not use `define-generic` for every generic procedure, -because `define-method` will create the generic procedure if needed. -So, it would mean adding a `define-generic` form for every generic -function that should be documented. Would it make sense to allow -documentation strings for methods, too? The documentation for a -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. +`defmethod` also accepts documentation strings, but Guile’s +`define-method` does not. ## Generics cannot be merged outside of a module -- cgit v1.2.3