From: Andy Wingo <wingo@pobox.com>
To: Jan Wedekind <jan@wedesoft.de>
Cc: 24454-done@debbugs.gnu.org
Subject: bug#24454: GOOPS problem with GNU Guile 2.1.4
Date: Wed, 22 Feb 2017 23:11:55 +0100 [thread overview]
Message-ID: <874lzlyixg.fsf@pobox.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1609172132190.7686@wedemob> (Jan Wedekind's message of "Sat, 17 Sep 2016 21:43:32 +0100 (BST)")
On Sat 17 Sep 2016 22:43, Jan Wedekind <jan@wedesoft.de> writes:
> The following program works fine under GNU Guile 2.0.12:
>
> (use-modules (oop goops))
> (define-generic native-type)
> (define-method (native-type (i <integer>) . args) 0)
> (define-method (native-type (i <real>) . args) 1)
> (define-method (native-type (b <boolean>) . args) 2)
>
> (native-type 1)
> (native-type 1.3)
> (native-type #f)
> (native-type 1 1.2)
> (native-type 1.4 2)
> (native-type 1.4 2 3)
> (native-type 1.4 1.5)
> (native-type #f #t)
>
> However under GNU Guile 2.1.4 [1] it fails with an error in
> "multiple-arity-dispatcher":
Thanks for the bug report! Fixed in master.
> Getting the backtrace didn't work:
Oops :P I fixed this too.
Cheers,
Andy
next prev parent reply other threads:[~2017-02-22 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 20:43 bug#24454: GOOPS problem with GNU Guile 2.1.4 Jan Wedekind
2017-02-22 22:11 ` Andy Wingo [this message]
2017-02-26 9:47 ` Jan Wedekind
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=874lzlyixg.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=24454-done@debbugs.gnu.org \
--cc=jan@wedesoft.de \
/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).