From: Kevin Ryde <user42@zip.com.au>
Cc: Guile-Devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Document pitfalls with `define-class' and `#:init-value'
Date: Fri, 29 Sep 2006 11:15:47 +1000 [thread overview]
Message-ID: <874purh3r0.fsf@zip.com.au> (raw)
In-Reply-To: <87hcyrh5eu.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 29 Sep 2006 10:39:53 +1000")
I wrote:
>
> Yes.
(Which is not to say I'm sure it'd look better, just an idea. Those
bits don't seem like they should be terribly difficult, a niceish or
typical example of each is probably plenty.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-09-29 1:15 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
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 [this message]
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=874purh3r0.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).