unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: vm status update, a.k.a. yowsers batman it's february already
Date: Tue, 03 Feb 2009 23:34:09 +0000	[thread overview]
Message-ID: <87myd3hz7y.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3iqnsfurl.fsf@pobox.com> (Andy Wingo's message of "Mon\, 02 Feb 2009 21\:28\:46 +0100")

Andy Wingo <wingo@pobox.com> writes:

>  * Just as we have a tower compilers (and thus languages), we now have a
>    tower of /decompilers/. Currently I've only implemented
>    value->objcode (only valid for values of type program or objcode),
>    objcode->bytecode, and bytecode->assembly, but it's possible to
>    implement passes decompiling all the way back to Scheme.
>
>    Or JavaScript! That's the crazy thing: since multiple languages exist
>    on top of one substrate, decompilers allow us to do language
>    translation -- what Guile originally wanted to do, but as artifact
>    rather than as mechanism.

That does sound interesting.  But it sounds more like something
educational to me, rather than a solution to the original translation
desire.  For example, it would allow us to show people the equivalent
of a given Scheme program in their own preferred language - which
would ultimately be helpful for teaching people Scheme.  And by adding
more sophisticated decompilation passes it might allow us to
demonstrate how a given program can be written (through provable
transformations) in several different ways, and consider which ways
are conventionally considered to be more elegant.

But is that the kind of thing that you had in mind, or have I missed
your point?

Regards,
        Neil




  parent reply	other threads:[~2009-02-03 23:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 20:28 vm status update, a.k.a. yowsers batman it's february already Andy Wingo
2009-02-02 20:50 ` Ludovic Courtès
2009-02-03 23:34 ` Neil Jerram [this message]
2009-02-04  0:34   ` Andy Wingo
2009-02-05 20:43     ` Neil Jerram

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=87myd3hz7y.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).