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>, 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 04:10:01 +0000	[thread overview]
Message-ID: <87y5dcp1ba.fsf@Kagami.home> (raw)
In-Reply-To: <291AEF3E-DF88-421B-AE2E-8FFAD005A39B@gnu.org> (Gary V. Vaughan's message of "Mon, 25 Mar 2013 09:21:21 +0700")

"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.

-- 
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  4:10 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 [this message]
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=87y5dcp1ba.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).