From: Ian Price <ianprice90@gmail.com>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Compilation to js [Update]
Date: Tue, 20 Jun 2017 23:35:24 +0100 [thread overview]
Message-ID: <CACpaFSTKn1sRbnKh3zUqe-evGDZwKhsJxKEakf7Z2RmvBDVrGA@mail.gmail.com> (raw)
In-Reply-To: <87lgom1j2u.fsf@web.de>
I would like to be able to access Javascript functions from Scheme,
possibly with a (system foreign) type API, but this is not a priority
at the moment. Getting as much of Scheme as possible working is the
main thing. On my list, you could put it as the unspoken 5th stage.
As for residualisation, it's not a technical term. More accurate
terminology would be serialisation of syntax objects. Maybe you can
interpret my use of "residue", as being partly negative, as residue is
something left over at the end of a process. Syntax objects are quite
big, (in one experiment I did today, it was half the size of the
output) and if possible, I'd like to avoid emitting them, where
possible, since this is going to be sent over the network.
next prev parent reply other threads:[~2017-06-20 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 18:43 Compilation to js [Update] Ian Price
2017-06-20 20:48 ` Arne Babenhauserheide
2017-06-20 20:51 ` not being residualised ff
2017-06-21 0:06 ` Mark H Weaver
2017-06-20 22:35 ` Ian Price [this message]
2017-06-20 23:58 ` Compilation to js [Update] Mark H Weaver
2017-06-21 21:01 ` Arne Babenhauserheide
-- strict thread matches above, loose matches on Subject: below --
2017-08-09 15:20 Compilation to JS [Update] Ian Price
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=CACpaFSTKn1sRbnKh3zUqe-evGDZwKhsJxKEakf7Z2RmvBDVrGA@mail.gmail.com \
--to=ianprice90@gmail.com \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.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).