This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: thanks
- To: Jim Blandy <jimb at red-bean dot com>
- Subject: Re: thanks
- From: Han-Wen Nienhuys <hanwen at cs dot uu dot nl>
- Date: Sun, 5 Dec 1999 16:58:13 +0100 (CET)
- Cc: guile at sourceware dot cygnus dot com, jantien at xs4all dot nl
- References: <14408.17885.875301.897078@dokkum.cs.uu.nl><m3iu2el61g.fsf@savonarola.red-bean.com>
- Reply-To: hanwen at cs dot uu dot nl
(gratuitious CC to the guile-list)
jimb@red-bean.com writes:
>
> > Just a quick note to say thanks for the good work you've been doing
> > on GUILE:
> >
> > Thanks!
>
> Thanks, Han-Wen. I do wish I'd been able to help you more with
> Guile-ifying LilyPond, but I don't think I had much insight into the
> issues.
Integrating GUILE has learned me much about how interpreters and
Scheme works. I had to skip to the .c sources directly to find out
what I was looking for many times. I don't have a problem with that,
since the sources are very clean, but others may have.
(climbing soapbox)
So I think that there is definitely a need for more documentation.
Also, I think that the gh_ interface is not very useful, if you build
an application that has more complex functionality than an interpreter
with a REP loop.
Browsing lily sources reveals calls to scm_assoc, scm_assoc_set_x,
scm_reverse ,scm_mkstrpor, scm_ftell, scm_eval_x, scm_read,
scm_fill_input, scm_puts, scm_unprotect_object, scm_protect_object,
and lots more. I don't think the gh_ interface is rich enough for my
purposes, and frankly, I still don't know what it is for exactly.
> Good luck!
Thanks, we're getting there. Replacing C pointers with SMOB
references is dramatically simplifying our code. GUILE rules, SMOBS
kick ass!
--
Han-Wen Nienhuys, hanwen@cs.uu.nl ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html