From: Arne Babenhauserheide <arne_bab@web.de>
To: Ian Price <ianprice90@gmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Compilation to js [Update]
Date: Wed, 21 Jun 2017 23:01:29 +0200 [thread overview]
Message-ID: <87mv913viu.fsf@web.de> (raw)
In-Reply-To: <CACpaFSTKn1sRbnKh3zUqe-evGDZwKhsJxKEakf7Z2RmvBDVrGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Ian Price <ianprice90@gmail.com> writes:
> 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.
ok. Thank you!
> 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.
Ah, the residuum is something I know :)
Sounds great!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-21 21:01 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 ` Compilation to js [Update] Ian Price
2017-06-20 23:58 ` Mark H Weaver
2017-06-21 21:01 ` Arne Babenhauserheide [this message]
-- 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=87mv913viu.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=ianprice90@gmail.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).