From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: scheme to C
Date: Fri, 04 Oct 2002 12:20:43 -0700 [thread overview]
Message-ID: <E17xY0B-0005X2-00@giblet> (raw)
In-Reply-To: <3D198B30.4D776935@carme.sect.mce.hw.ac.uk> (peteri@carme.sect.mce.hw.ac.uk)
From: "Mr. Peter Ivanyi" <peteri@carme.sect.mce.hw.ac.uk>
Date: Wed, 26 Jun 2002 10:36:48 +0100
Reading some past messages from the list, I have the impression that
there used to be a compiler from scheme to C (hobbit ?) but it is
broken now. Can somebody tell me how it is broken, does not work at
all, etc ... ? How difficult to make hobbit work again ? Does it
require major changes ?
these questions were asked by the compiler author himself (revisiting
guile after a few years abroad), but the answers are still not known.
however, they are *knowable* and probably continued 1.4.1.x hacking will
teach me enough to provide them (hobbit revival is the explicitly
intended side effect of answering these questions, after all).
i was hoping current crop of guile mungers could help, but now i'm more
realistic about their abilities and inclinations. if you would like to
help, i suggest a hands-on approach: build {guile,hobbit}-1.3.4, run
them, take notes, try hobbit-1.3.4 w/ guile-1.4.x, take notes on what
breaks, post notes for discussion.
perhaps a small subset of programs works w/ hobbit-1.3.4/guile-1.4.x.
if so, we can collect them under examples/compilation/, add appropriate
configure.in checks for hobbit and augment the "make installcheck" flow.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-10-04 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 9:36 scheme to C Mr. Peter Ivanyi
2002-10-04 19:20 ` Thien-Thi Nguyen [this message]
2002-10-07 8:39 ` Bernard Urban
2002-10-07 13:19 ` Marius Vollmer
2002-10-07 17:08 ` Thien-Thi Nguyen
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=E17xY0B-0005X2-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).