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: Tue, 20 Jun 2017 22:48:41 +0200 [thread overview]
Message-ID: <87lgom1j2u.fsf@web.de> (raw)
In-Reply-To: <CACpaFST3_RYrbsb1e9NB98yRa7Kk1U4p_q0fDr9V_106j7yhvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
Hi Ian,
Ian Price <ianprice90@gmail.com> writes:
> I think the approach using the dominator functions in (language cps
> utils) is the right way, and is giving the results I want. I intend to
> write a blog post shortly explaining how dominators / cps-soup work
> and how to compile from it for other people who may be interested in
> these low level guile details.
That sounds great!
> That said, you can take some scheme files and compile them with the
> usual functions, e.g.
>
> (compile-file "/tmp/foo.scm" #:to 'javascript #:output-file "/tmp/foo.js")
Is there already a clean way to run javascript functions from scheme —
for example accessing the DOM? That would directly allow pure Guile web
development.
> What's next? Number 2 on my list from last time was
>> Complete porting boot-9 to js (in particular, the guile module system)
> so this is what I intend to do. This will allow us to run much more
> complicated programs, and you won't need to keep reimplementing
> functions like map.
>
> Another issue is with macros, which are not being residualised now
> that their representation was changed, so I'll do that too.
What does residualization of macros mean? (I feel I’m missing language here).
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-20 20:48 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 [this message]
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
-- 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=87lgom1j2u.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).