From: Ben Elliston <bje@wasabisystems.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: guile 1.6.4 a bit faster?
Date: Sat, 19 Jul 2003 14:13:00 -0000 [thread overview]
Message-ID: <87k7airuel.fsf@sashimi.wasabisystems.com> (raw)
In-Reply-To: <16149.29891.38503.939572@casey.transmeta.com>
Doug Evans <dje@transmeta.com> writes:
> It cost nothing to have the support.
> If it bitrots let me fix it.
That's not true. It was costing something, because there were kludges
in CGEN to handle differing Scheme syntax supported by Guile and
Hobbit. It also made the Makefiles slightly more complex and, at the
time, I opted to remove it for clarity.
> And the fun factor was just way too huge, which was the whole point
> of cgen. After several miserable years on (pre-egcs) gcc, I
> desparately needed to rediscover a joy of hacking.
I don't disagree :-)
> The cynic in me wonders if there was some internal political reason
> for its removal.
Where have I heard that before? No, it was just me trying to get my
head around CGEN at the time and the simpler, the better.
Ben
next prev parent reply other threads:[~2003-07-16 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 0:26 Doug Evans
2003-07-16 10:03 ` Ben Elliston
2003-07-16 15:52 ` Ben Elliston
2003-07-16 16:02 ` Doug Evans
2003-07-19 14:13 ` Ben Elliston [this message]
2003-07-16 22:35 ` 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=87k7airuel.fsf@sashimi.wasabisystems.com \
--to=bje@wasabisystems.com \
--cc=cgen@sources.redhat.com \
--cc=dje@transmeta.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).