resolve() function is called.
I assume the first step would be to get that little REPL console working.
The links above are to the source for the current iteration of the REPL, which embraces this technique. There is a very long way to go in terms of error handling, exceptions, and being truly easy-to-use for a casual scripter…really it was just a proof-of-concept to get the model out the door.
Here’s a page with the REPL: http://hostilefork.com/media/shared/replpad-js/
It tries to attack the basic problems, while trying to throw in a couple of Ren-Garden-isms. Do shift-enter for multi-line input, and you can try something that does a loop containing an INPUT and a PRINT. Cancellation still needs work (the previous iteration of the demo handled it, but it hasn’t been accomodated by this one yet). There are some attempts at undo-ability across evaluations.
The codebase tries to stay within the realms of defined behavior at the abstraction level of C, and so it has mechanically been able to compile with emscripten for some time. But when it comes down to making it work in a way that is favorable, code tends not to design or write itself.
And the language has not stood still. Whether it’s things like being able to feed left hand sides into PATH! or truly invisible COMMENTs or pushing the evaluator with things like MATCH, there are a lot of new ideas to show!