unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: 23404-done@debbugs.gnu.org
Subject: bug#23404: Infinite recursion in GOOPS in Guile 2.2
Date: Tue, 28 Feb 2017 16:12:46 +0100	[thread overview]
Message-ID: <87lgsql575.fsf@pobox.com> (raw)
In-Reply-To: <87twijygon.fsf@dustycloud.org> (Christopher Allan Webber's message of "Fri, 29 Apr 2016 21:27:20 -0500")

On Sat 30 Apr 2016 04:27, Christopher Allan Webber <cwebber@dustycloud.org> writes:

> 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))

This appears to be fixed, somehow (?).  Please reopen if you can still
produce the bug.

Andy





      reply	other threads:[~2017-02-28 15:12 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
2016-04-30  2:27 ` Christopher Allan Webber
2017-02-28 15:12   ` Andy Wingo [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=87lgsql575.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=23404-done@debbugs.gnu.org \
    --cc=cwebber@dustycloud.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).