From: Rob Browning <rlb@defaultvalue.org>
To: 39395@debbugs.gnu.org
Subject: bug#39395: GOOPS generic promotion fails for nary functions
Date: Fri, 07 Feb 2020 00:39:15 -0600 [thread overview]
Message-ID: <87o8ua2964.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87a7606cad.fsf@trouble.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> And then I found that the the manual says this:
>
> If symbol was previously bound to a Scheme procedure (or
> procedure-with-setter), the old procedure (and setter) is incorporated
> into the new generic function as its default procedure (and setter).
>
> So I wondered if this might be a bug, or was expected behavior. It's
> also easy to work around -- just change the first define to a
> define-method.
Not sure if this might be related. With guile-3.0
(use-modules (oop goops))
(define x close)
(define-generic x)
produces:
$ guile-3.0 -s test.scm
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /home/rlb/test.scm
;;; /home/rlb/test.scm:5:0: warning: shadows previous definition of `x' at /home/rlb/test.scm:4:0
;;; compiled /home/rlb/.cache/guile/ccache/3.0-LE-8-4.2/home/rlb/test.scm.go
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
prev parent reply other threads:[~2020-02-07 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 19:04 bug#39395: GOOPS generic promotion fails for nary functions Rob Browning
2020-02-07 6:39 ` Rob Browning [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8ua2964.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=39395@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).