From: Marius Vollmer <mvo@zagadka.ping.de>
Subject: Re: ANNOUNCE: Common Music for Guile
Date: 26 Oct 2002 14:00:09 +0200 [thread overview]
Message-ID: <87k7k5s94m.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3adl29krr.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Marius Vollmer <mvo@zagadka.ping.de> wrote:
> > Rick Taube <taube@uiuc.edu> writes:
> >> There were really only a few things I missed from CLTL2 (besides loop :) )
> >>
> >> 1) a compiler
> >> 2) a compiler
> >> 3) a compiler
> >
> > We'll get to that eventually, I hope. And once we have 1, points 2
> > and 3 should be easy.
>
> What form would that be likely to take? Maybe a gcc frontend?
The first compiler will likely only be able to write our tree-codes to
disk.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-10-26 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 13:54 ANNOUNCE: Common Music for Guile Rick Taube
2002-10-18 21:15 ` Marius Vollmer
2002-10-25 23:10 ` Paul Jarc
2002-10-26 12:00 ` Marius Vollmer [this message]
2002-10-26 3:56 ` Clinton Ebadi
2002-11-03 17:33 ` Marius Vollmer
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=87k7k5s94m.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
/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).