From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: What new libraries or functionality does Guile need?
Date: Mon, 21 Jul 2008 08:34:29 +0200 [thread overview]
Message-ID: <87abgb924q.fsf@ambire.localdomain> (raw)
In-Reply-To: <300493.30487.qm@web37903.mail.mud.yahoo.com> (Mike Gran's message of "Fri, 18 Jul 2008 10:13:04 -0700 (PDT)")
() Mike Gran <spk121@yahoo.com>
() Fri, 18 Jul 2008 10:13:04 -0700 (PDT)
If you could ask someone to write a library or package a set of
functionality for Guile that it doesn't currently have, what
would it be?
I would ask for an API-upgrade program. This program would scan
C source to identify API elements that newer Guile no longer
supports and substitute them with equivalent constructs that newer
Guile does support. It should be able to operate w/o modifying
the original tree, support an interactive repl for human-override,
and keep a database of the override decisions (w/ annotations).
The database should be exportable and have a published access /
modification protocol.
thi
next prev parent reply other threads:[~2008-07-21 6:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 17:13 What new libraries or functionality does Guile need? Mike Gran
2008-07-18 17:39 ` Julian Graham
2008-07-18 18:32 ` Andre Kuehne
2008-07-19 0:40 ` Jose A. Ortega Ruiz
2008-07-19 5:49 ` Maciek Godek
2008-07-19 18:10 ` Bill Schottstaedt
2008-07-20 20:42 ` Ludovic Courtès
2008-07-20 22:35 ` Mike Gran
2008-07-21 6:34 ` Thien-Thi Nguyen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 18:38 Mike Gran
2008-07-18 19:37 dsmich
2008-07-18 19:43 dsmich
[not found] <cmu-lmtpd-23333-1216458306-3@mail-imap1.uio.no>
2008-07-19 11:08 ` Kjetil S. Matheussen
2008-07-21 16:02 ` JonWilson
2008-07-22 13:09 ` Bill Schottstaedt
[not found] <cmu-lmtpd-5742-1216742728-1@mail-imap1.uio.no>
2008-07-22 16:24 ` Kjetil S. Matheussen
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=87abgb924q.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=spk121@yahoo.com \
/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).