History

joeduffy 5bdb535c54 Begin doing evaluation This change checks in an enormously rudimentary interpreter. There is a lot left to do, as evidenced by the countless TODOs scattered throughout pkg/compiler/eval/eval.go. Nevertheless, the scaffolding and some important pieces are included in this change. In particular, to evaluate a package, we must locate its entrypoint and then, using the results of binding, systematically walk the full AST. As we do so, we will assert that aspects of the AST match the expected shape, including symbols and their types, and produce value objects for expressions. An unwind structure is used for returns, throws, breaks, and continues (both labeled and unlabeled). Each statement or expression visitation may optionally return one and its presence indicates that control flow transfer is occurring. The visitation logic then needs to propagate this; usually just by bailing out of the current context immediately, but sometimes -- as is the case with TryCatchBlock statements, for instance -- the unwind is manipulated in more "interesting" ways. An Object structure is used for expressions yielding values. This is a "runtime object" in our system and is comprised of three things: 1) a Type (essentially its v-table), 2) an optional data pointer (for tagged primitives), and 3) an optional bag of properties (for complex object property values). I am still on the fence about whether to unify the data representations. The hokiest aspect of this change is the scoping and value management. I am trying to avoid needing to implement any sort of "garbage collection", which means our bag-of-values approach will not work. Instead, we will need to arrange for scopes to be erected and discarded in the correct order during evaluation. I will probably tackle that next, along with fleshing out the many missing statement and expression cases (...and tests, of course).		2017-01-25 10:13:06 -08:00
..
cmd	Fix truncated output...again	2017-01-17 14:54:15 -08:00
lib	Begin doing evaluation	2017-01-25 10:13:06 -08:00
tests	Add optional properties	2017-01-23 11:14:24 -08:00
.gitignore	Add a new harness for test cases	2017-01-08 15:20:46 -06:00
README.md	Implement the MuIL AST	2016-12-30 15:34:49 -08:00
mujs	Add a handy executable wrapper for MuJS	2017-01-08 15:34:10 -06:00
package.json	Add support for YAML project files to MuJS	2017-01-17 12:09:57 -08:00
tsconfig.json	Do a bit of house-cleaning	2017-01-13 10:42:50 -08:00
tslint.json	Upgrade to latest TSLint, and compile cleanly	2016-12-31 11:16:36 -08:00
yarn.lock	Add support for YAML project files to MuJS	2017-01-17 12:09:57 -08:00

README.md

MuJS

This directory contains Mu's JavaScript compiler.

It implements a subset of JavaScript with TypeScript-style type annotations, and can compile that subset into MuPack/IL.