From: Tristan Colgate <tcolgate@gmail.com>
To: guile-user@gnu.org
Subject: Does anyone have an applicable struct example
Date: Fri, 25 Jun 2010 10:14:06 +0100 [thread overview]
Message-ID: <AANLkTilK-JEqH10LimscAxsfLS6d5dTgV8Qh8OWoYkcl@mail.gmail.com> (raw)
Hi all,
I'd like to make use of the applicable structs feature but am
running into problems.
From what I can gather from the release note that mentions it, the
following should work,
instead, I get a segfault.
scheme@(guile-user)> (define <mything-vtable> (make-struct
<applicable-struct-vtable> 0))
scheme@(guile-user)> (define mything (make-struct <mything-vtable> 0
(lambda()(display "some code")(newline))))
Segmentation fault (core dumped)
Looking around goops.scm I can see some classes for applicable structs
that look a bit nicer, but these seem
to use set-object-procedure! which isn't exported (and I can't find a
definition)....
scheme@(guile-user)> (use-modules (oop goops))
scheme@(guile-user)> (define-class <myclass> (<applicable-struct>))
scheme@(guile-user)> (make <myclass> #:procedure (lambda()(display
"some code")(nelwine)))
<stdin>:5:58: warning: possibly unbound variable `nelwine'
Throw to key `unbound-variable':
ERROR: In procedure module-lookup:
ERROR: Unbound variable: set-object-procedure!
I tried using a generic instead but it didn't make much difference.
What am I doing wrong?
--
Tristan Colgate-McFarlane
----
"You can get all your daily vitamins from 52 pints of guiness, and a
glass of milk"
next reply other threads:[~2010-06-25 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 9:14 Tristan Colgate [this message]
2010-06-28 10:06 ` Does anyone have an applicable struct example Tristan Colgate
2010-06-29 2:16 ` Nala Ginrut
2010-06-29 9:56 ` Andy Wingo
2010-08-29 18:48 ` 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=AANLkTilK-JEqH10LimscAxsfLS6d5dTgV8Qh8OWoYkcl@mail.gmail.com \
--to=tcolgate@gmail.com \
--cc=guile-user@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).