From: Christopher Allan Webber <cwebber@dustycloud.org>
To: 25211@debbugs.gnu.org
Subject: bug#25211: GOOPS #:class alocation broken in Guile 2.2
Date: Thu, 15 Dec 2016 13:39:47 -0600 [thread overview]
Message-ID: <87y3zhugl8.fsf@dustycloud.org> (raw)
In Guile 2.2:
(define-class <foo> ()
(bar #:allocation #:class
#:init-value 'baz))
(slot-definition-allocation (class-slot-definition <foo> 'bar))
=> #:instance
In Guile 2.0 this properly returns #:class.
Also, curiously, Guile 2.2 breaks if you present the keywords in the
wrong order:
(define-class <foo> ()
(bar #:allocation #:class
#:init-value 'baz))
oop/goops.scm:352:0: In procedure class-precedence-list:
oop/goops.scm:352:0: In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): #:init-value
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
scheme@(#{8sync}# systems actors) [1]> ,bt
In current input:
1205:0 4 (_)
In oop/goops.scm:
2978:4 3 (_ _ . _)
811:17 2 (%prep-layout! #<<class> <foo> 30b1b40>)
767:19 1 (%compute-layout _ 0 #f)
352:0 0 (class-precedence-list _)
I'm guessing that's related!
next reply other threads:[~2016-12-15 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 19:39 Christopher Allan Webber [this message]
2017-03-01 14:38 ` bug#25211: GOOPS #:class alocation broken in Guile 2.2 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=87y3zhugl8.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=25211@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).