From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Implementation Language
Date: Sat, 29 Jul 2000 09:26:00 -0000 [thread overview]
Message-ID: <14723.1398.258797.45090@casey.transmeta.com> (raw)
Ben Elliston writes:
> We've been running CGEN purely interpeted for several months now and no one
> is finding the speed to be a problem at all.
The smob class implementation is gone too though.
Debugging was much easier with it.
[Of course, for those tuning in late, should the implementation
remain in Guile, yes, we'll want to switch to goops (IMO of course).]
That's probably the first decision we need to reach:
do we stick with Guile? There's no other politically correct
choice for a Scheme implementation. Or do we switch to C? (/C++?).
[I can here the cackles now ...]
I think speed of code generation is important, but I also think
there's no reason why a Scheme implementation can't satisfy that.
However, I think the current Guile implementation has a _long_ way to go
in this regard, and I'm not convinced it will ever get there.
next reply other threads:[~2000-07-29 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-29 9:26 Doug Evans [this message]
2000-07-31 18:31 ` Frank Ch. Eigler
2000-08-01 1:00 ` Ben Elliston
2000-08-02 17:10 ` Frank Ch. Eigler
2000-08-03 0:03 ` Ben Elliston
2000-08-03 7:07 ` matthew green
2000-08-03 9:31 ` Doug Evans
2000-08-03 9:49 ` Doug Evans
2000-08-03 16:23 ` Ben Elliston
2000-08-03 18:31 ` Doug Evans
2000-08-03 16:22 ` Ben Elliston
2000-08-05 10:16 ` Doug Evans
2000-08-06 14:52 ` Frank Ch. Eigler
2000-08-06 15:27 ` Ben Elliston
2000-08-07 14:01 ` Doug Evans
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14723.1398.258797.45090@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=bje@redhat.com \
--cc=cgen@sources.redhat.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).