unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: [PATCH] Document pitfalls with `define-class' and `#:init-value'
Date: Thu, 28 Sep 2006 08:56:54 +0100	[thread overview]
Message-ID: <87ac4k8lvd.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87bqp0dezx.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 28 Sep 2006 10:14:10 +1000")

Kevin Ryde <user42@zip.com.au> writes:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> Thanks; I've applied most of it to HEAD,
>
> If it's any good then it's worth having in the 1.8 branch, no need for
> doc clarifications to wait the 3 years between major releases :-).

Agreed; done.

>> with slight edits so as not to make the point too many times.
>
> Looks a little verbose still.

Yes, but I think it's useful all the same.

>  Perhaps separating each #:init-foo
> would be clearer.

Do you mean making separate @deffn's, or just paragraph breaks between
the sentences covering the different keywords?

Regards,
     Neil



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-09-28  7:56 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 [this message]
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=87ac4k8lvd.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).