public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: Porting CGEN to other Scheme implementations
Date: Thu, 27 Jan 2005 19:31:00 -0000	[thread overview]
Message-ID: <vt2pszqsmjt.fsf@zenia.home> (raw)
In-Reply-To: <16889.13744.130693.210940@casey.transmeta.com>

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]


Doug Evans <dje@transmeta.com> writes:
> Jim Blandy writes:
>  > 
>  > I'm interested in porting CGEN to MzScheme.  MzScheme has an active
>  > development community, and (of particular interest to Red Hat) an
>  > actively maintained Scheme-to-C compiler.  I'd like to talk about how
>  > I'm thinking of approaching it, and see what folks think.
> 
> How good is the debugging capabilities of MzScheme?
> Compared to Guile?  1/2 :-)

MzScheme has much better debugging capabilities, I think.  They have
an IDE called DrScheme which does all kinds of great stuff.  Here's a
screen shot of DrScheme giving me an error backtrace:


[-- Attachment #2: DrScheme error backtrace screenshot --]
[-- Type: image/png, Size: 41879 bytes --]

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]


> OOC, how come Redhat has a particular interest in a Scheme-to-C
> compiler?

Well, just speed.

> btw, one day I want to port CGEN to Rscheme, for fun's sake.

Absolutely!  May the most useful win.

  reply	other threads:[~2005-01-27 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 18:30 Jim Blandy
2005-01-27 18:40 ` Doug Evans
2005-01-27 19:31   ` Jim Blandy [this message]
2005-01-27 19:33 ` Frank Ch. Eigler

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=vt2pszqsmjt.fsf@zenia.home \
    --to=jimb@redhat.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).