unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: How to convert from Emacs Lisp to Guile
Date: Sun, 20 Jun 2010 21:33:51 +0200	[thread overview]
Message-ID: <87eig1ebxc.fsf@ambire.localdomain> (raw)
In-Reply-To: <87vd9dy14t.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 20 Jun 2010 21:06:42 +0200")

() ludo@gnu.org (Ludovic Courtès)
() Sun, 20 Jun 2010 21:06:42 +0200

   FWIW I’d prefer to avoid auto-extracted documentation.  Presumably it
   would take a little bit of writing to provide more introductory text and
   transitions between the different parts of the API.

I understand.  It won't be difficult to fill things out this way.

   [placement]

   Perhaps under “Simple Generic Data Types”, after “Strings”.
   What do you think?

That doesn't seem right.  A gap-buffer is (conceptually) simple, but this
particular implementation is not generic in the sense that the only supported
fundamental type at the moment is the single ubyte (not even the character).

   [(simple) test cases file]

   Just drop it under ‘test-suite/tests’, with a ‘define-module’.  A few
   comments on what the tests do would be welcome too as it looks a bit
   dense at first sight.  :-)

OK.  I'll post a patch to guile-devel in the next few days.

thi



      reply	other threads:[~2010-06-20 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18  8:48 How to convert from Emacs Lisp to Guile Cecil Westerhof
2010-06-18 15:07 ` Ludovic Courtès
2010-06-18 17:19   ` Thien-Thi Nguyen
2010-06-20 14:03     ` Ludovic Courtès
2010-06-20 17:51       ` Thien-Thi Nguyen
2010-06-20 19:06         ` Ludovic Courtès
2010-06-20 19:33           ` Thien-Thi Nguyen [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=87eig1ebxc.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@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).