unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Ian Price <ianprice90@googlemail.com>
To: "Gary V. Vaughan" <gary@gnu.org>
Cc: Guile User <guile-user@gnu.org>, Reuben Thomas <rrt@sc3d.org>,
	Zile bugs <bug-zile@gnu.org>
Subject: Re: Anniversary hack: Zile editor with Guile support
Date: Mon, 25 Mar 2013 02:13:00 +0000	[thread overview]
Message-ID: <8738vkqlar.fsf@Kagami.home> (raw)
In-Reply-To: <6AE6C7E8-7B28-40FA-B607-1D46FA52EB80@gnu.org> (Gary V. Vaughan's message of "Fri, 22 Mar 2013 10:10:18 +0700")

"Gary V. Vaughan" <gary@gnu.org> writes:

> Rather than byte-code to byte-code translation, I was rather thinking of either:
>
>   1. Tweaking zlc to be capable of compiling guile scheme directly to Lua (and
>      then easily from there to Lua bytecodes); or
>   2. Running Zile with the Guile implementation of Lua, and getting Guile as
>      an extension language for free.
>
> The first, I can do, though it's a long time since I paid attention to Guile,
> so I'd need guidance and/or test-cases from someone familiar with it to make
> sure my implementation would be compatible with canonical Guile Scheme.

Rather than going for Scheme integration, it'd be better to target
tree-il, which is the level below it.

> The second, I was asking about because I was initially drawn to Guile during
> the era when it was being touted as a good compiler target platform to become
> a runtime for code written in any language and then translated to Guile Scheme
> before execution.  But, my impression is that this work stalled and/or failed?

I'd say stalled, rather than failed.  We haven't heard from the
"maintainer" for two years now, and I've been periodically asking around
for people to pick it up, but without any luck.  The intersection of
people interested in Guile and Lua is pretty small, it seems.

-- 
Ian Price -- shift-reset.com

"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"



  reply	other threads:[~2013-03-25  2:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOnWdoggx6YWV_VUuYcdosvsXFwYXzua57NaUTa7ZT3RiUtvOA@mail.gmail.com>
     [not found] ` <4CB5C160-9728-4784-ABA1-E8BDFC825990@vaughan.pe>
2013-03-22  1:13   ` Anniversary hack: Zile editor with Guile support Gary V. Vaughan
2013-03-22  2:43     ` Mike Gran
2013-03-22  3:10       ` Gary V. Vaughan
2013-03-25  2:13         ` Ian Price [this message]
2013-03-25  2:21           ` Gary V. Vaughan
2013-03-25  4:10             ` Ian Price
2013-03-25  4:22               ` Gary V. Vaughan
2013-03-25  6:24                 ` Ian Price
2013-03-25  7:06                   ` Gary V. Vaughan
2013-03-25  2:52           ` Nala Ginrut
2013-03-22 11:05     ` Ludovic Courtès
2013-03-23  1:32       ` Nala Ginrut
2012-02-13  0:51 Mike Gran
2012-02-13 14:25 ` Bernardo Ezequiel Contreras
2012-02-13 15:37   ` Mike Gran
2012-02-13 22:40     ` Ludovic Courtès
2012-02-13 14:27 ` Ludovic Courtès
2012-02-14  5:46   ` Mike Gran

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=8738vkqlar.fsf@Kagami.home \
    --to=ianprice90@googlemail.com \
    --cc=bug-zile@gnu.org \
    --cc=gary@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=rrt@sc3d.org \
    /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).