From: Christopher Allan Webber <cwebber@dustycloud.org>
To: 23404@debbugs.gnu.org
Subject: bug#23404: Infinite recursion in GOOPS in Guile 2.2
Date: Fri, 29 Apr 2016 21:26:52 -0500 [thread overview]
Message-ID: <87vb2zygpf.fsf@dustycloud.org> (raw)
In-Reply-To: <87wpngx7n7.fsf@dustycloud.org>
It looks like my example was incomplete. It turns out loading and
passing in an srfi-9 record is critical to instantiating the bug.
Why? I'm not sure...
(use-modules (oop goops)
(srfi srfi-9))
(define-class <some-class> ())
(define-record-type <some-record>
(make-some-record foo)
some-record?
(foo some-record-foo))
(define-method (time-to-break (some-class <some-class>) not-a-class)
(display "We're never going home are we?\n"))
;; Now it'll break
(time-to-break (make <some-class>) (make-some-record 1))
next prev parent reply other threads:[~2016-04-30 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 0:27 bug#23404: Infinite recursion in GOOPS in Guile 2.2 Christopher Allan Webber
2016-04-30 2:26 ` Christopher Allan Webber [this message]
2016-04-30 2:27 ` Christopher Allan Webber
2017-02-28 15:12 ` Andy Wingo
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=87vb2zygpf.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=23404@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).