public inbox for
 help / color / mirror / Atom feed
From: Rob Browning <>
To: Ariel Rios <>
Subject: Re: Converting defs file unto guile-wrap code
Date: Tue, 29 May 2001 22:05:00 -0000	[thread overview]
Message-ID: <87hey3mnpi.fsf@raven.localnet> (raw)
In-Reply-To: <991192650.2622.3.camel@soleil>

Ariel Rios <> writes:

> Now, Is these the correct approach to follow? It is obviously
> a very easy way of doing it.

It seems OK.  It's probably worth trying, and if you run in to
trouble, it should be quite easy to change to a normal parser.  My
experience has been that sometimes it's a little easier to just deal
with a straightforward parser, but it the job is simple enough, then
macros may be fine.

Anyway, writing a parser later if you need it would be easy:

  (define (compile-defs file-port)
    (let loop ((next-form (read)))
        ((eof-object? next-form) ...)
        ((null? next-form) ...)
        ((eq? 'define-enum (car next-form)) ...)
      (loop (read))))

or similar...

> Rob, do you think that the current defs format info is enough for
> g-wrap?

I haven't really seen the defs file in detail yet, but I suspect it
is, and if not, then we should be able to either enhance g-wrap, your
translator, or the defs spec to fix the problem.

BTW I've been told to go ahead with the g-wrap CVS module, so I should
be able to commit that this week sometime.  I'll also send you the
current (1/4 finished) info docs right now.

Rob Browning <> PGP=E80E0D04F521A094 532B97F5D64E3930

      reply	other threads:[~2001-05-29 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29 21:14 Ariel Rios
2001-05-29 22:05 ` Rob Browning [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hey3mnpi.fsf@raven.localnet \ \ \ \

* 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).