From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: GOOPS: Customizing class instantiation
Date: Thu, 28 Sep 2006 09:50:12 +0100 [thread overview]
Message-ID: <87lko474u3.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87irj9witv.fsf@laas.fr> ( Ludovic Courtès's message of "Wed, 27 Sep 2006 15:16:28 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> In short, the lesson is: one should use `make-class' (although
> it's undocumented) rather than `(make <class> ...)' when instantiating a
> new class.
Apologies for not playing earlier, but for the record I agree that
this is the right answer. The GOOPS code has make-xxx procedures that
can be used programmatically for all the important things (classes,
methods, generics etc.), and the define-xxx macros that we mostly use
are wrappers around these.
One final thought: recommend changing <my-class> to <my-metaclass> (if
you still need it, given make-class).
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2006-09-28 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 8:24 GOOPS: Customizing class instantiation Ludovic Courtès
2006-09-26 11:47 ` Ludovic Courtès
2006-09-26 15:26 ` Pat Lasswell
2006-09-27 8:20 ` Ludovic Courtès
2006-09-27 13:16 ` Ludovic Courtès
2006-09-28 8:50 ` Neil Jerram [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=87lko474u3.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).