From: Kevin Ryde <user42@zip.com.au>
Subject: Re: [PATCH] Document pitfalls with `define-class' and `#:init-value'
Date: Wed, 08 Mar 2006 10:52:09 +1100 [thread overview]
Message-ID: <87pskxke3a.fsf@zip.com.au> (raw)
In-Reply-To: <87oe0qt9vn.fsf@laas.fr> (Ludovic Courtès's message of "Wed, 01 Mar 2006 17:20:12 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> shared across all new instances of the class
That bit sounds fair, I it in. I think the rest labours the point a
little. Hopefully seeing init-thunk and init-form described is
enough.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-03-07 23:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 16:20 [PATCH] Document pitfalls with `define-class' and `#:init-value' Ludovic Courtès
2006-03-07 23:52 ` Kevin Ryde [this message]
2006-03-08 9:07 ` Ludovic Courtès
2006-03-08 20:25 ` Kevin Ryde
2006-03-21 8:12 ` Ludovic Courtès
2006-09-23 10:35 ` Neil Jerram
2006-09-25 7:42 ` Ludovic Courtès
2006-09-27 17:51 ` Neil Jerram
2006-09-28 0:14 ` Kevin Ryde
2006-09-28 7:56 ` Neil Jerram
2006-09-29 0:39 ` Kevin Ryde
2006-09-29 1:15 ` Kevin Ryde
2006-10-04 22:19 ` Neil Jerram
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=87pskxke3a.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).