public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, cgen@sources.redhat.com
Subject: Re: Implementation Language
Date: Thu, 03 Aug 2000 09:31:00 -0000	[thread overview]
Message-ID: <14729.40545.762999.300037@casey.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0008031701060.853-100000@moshpit.cygnus.com>

Ben Elliston writes:
 >    > [...] What's wrong exactly with the Guile implementation--if considered
 >    > as simply an implementation of R5RS?
 >    
 >    Nothing big AFAIK --- it's just tempting to depend on its extensions rather
 >    than using standard libraries like SLIB.
 > 
 > I think it's simple: we need to resist such temptations and write in
 > portable Scheme.

Modulo: we can write in C those parts we wish to
as long as a portable Scheme version also exists [e.g. cos.c,
not that I necessarily want to keep it in the long run,
but rather as an example of what I mean here.]

 > Do we have any performance issues with Guile?  

Yes!!!

 > Personally, I'd like to see us keep it and refine what we have.  As we know,
 > rewrites are rarely a panacea. :-)

But they're fun. :-)
And after we have at least one more big usage under our belt
[dynamic compilation?] and we have a proper function unit description
[plus related paraphenalia] I think we should take a step back
and review everything from the ground up.

  parent reply	other threads:[~2000-08-03  9:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-29  9:26 Doug Evans
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 [this message]
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=14729.40545.762999.300037@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=bje@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=fche@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).