From: "Gary V. Vaughan" <gary@gnu.org>
To: Ian Price <ianprice90@googlemail.com>
Cc: Guile User <guile-user@gnu.org>, Zile bugs <bug-zile@gnu.org>,
Reuben Thomas <rrt@sc3d.org>
Subject: Re: Anniversary hack: Zile editor with Guile support
Date: Mon, 25 Mar 2013 11:22:52 +0700 [thread overview]
Message-ID: <2BDCB6D4-B5B0-42D5-B5C8-FD0F2BD1D72A@gnu.org> (raw)
In-Reply-To: <87y5dcp1ba.fsf@Kagami.home>
Hi Ian,
On 25 Mar 2013, at 11:10, Ian Price <ianprice90@googlemail.com> wrote:
> "Gary V. Vaughan" <gary@gnu.org> writes:
>>>> 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.
>>
>> But surely, the point of having an Emacs that can be extended with Guile Scheme,
>> is that the user can feed Guile Scheme code to it? (1) above proposes compiling
>> the users Scheme to Lua bytecodes for sandboxed evaluation by Lua Zile.
>
> Of course we'd prefer Scheme, but I don't think that has to mean writing
> a new Guile-compatible Scheme implementation, and implementing Tree-IL
> doesn't preclude it.
>
> Guile is made up of several layers: Scheme/Tree-IL/GLIL/Assembly/etc.
> and we expose these through various modules. If you want to write a
> compiler for Scheme (in this case to Lua bytecode), we have the
> infrastructure available and documented for you.
>
> I suggest Tree-IL since that is the compilation target we recommend for
> new languages (both elisp and ecmascript compile to this), but if it is
> convenient for Lua bytecode, pick an even lower level one.
I think we are misunderstanding one another somewhere :(
I'm talking about this:
1. user writes some Guile Scheme, and feeds it to Lua Zile
2. Lua Zile runs zlc to translate Guile Scheme to Lua
3. Lua Zile runs luac to compile output of (2) to Lua bytecodes, and
saves the result to disk
4. Lua runtime executes file of Lua bytecodes.
I really don't see how Tree-IL fits in here, or makes loading and executing Guile
Scheme sources from Lua Zile any easier.
What am I missing?
Cheers,
--
Gary V. Vaughan (gary AT gnu DOT org)
next prev parent reply other threads:[~2013-03-25 4:22 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
2013-03-25 2:21 ` Gary V. Vaughan
2013-03-25 4:10 ` Ian Price
2013-03-25 4:22 ` Gary V. Vaughan [this message]
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=2BDCB6D4-B5B0-42D5-B5C8-FD0F2BD1D72A@gnu.org \
--to=gary@gnu.org \
--cc=bug-zile@gnu.org \
--cc=guile-user@gnu.org \
--cc=ianprice90@googlemail.com \
--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).