Compilation to JS [Update]

Hello Guilers, I am long overdue an update on the state of affairs of guile-js (the last was at the end of June). Last time I spoke, I had completed task 1 (cps old -> cps soup), and was starting work on task 2 (port boot-9[1]). I made a lot of headway on this task, and would categorise it as

Re: Compilation to js [Update]

Ian Price 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

Re: Compilation to js [Update]

Ian Price writes: > 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.

Re: Compilation to js [Update]

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

Re: Compilation to js [Update]

Hi Ian, Ian Price 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

Compilation to js [Update]

Hello guilers, I figure it's time for an update on what I've been working on for the past two weeks. I have mainly been working on updating the compiler to go from the old cps representation to the new cps-soup representation. This had a few false starts, but on the third attempt, I think the