yufengwng / table Goto Github PK

Don't necessarily need to support defining functions, but we need to be able to call functions. This will require refactoring the VM to support call frames and switching between frames.

Let's follow tradition here and use # as symbol for starting a line comment.

# this is a comment

Rather than waiting for full support of calling functions in #5, we'll add minimal support of handling call expressions and hook in a native print function for printing out values. Let's start with a println function that adds a newline at the end of the print.

For unit tests, each component should at least have one test per execution path.

For integration tests, ideally it should be a suite of script files so that it is agnostic to actual implementation and the suite can be ran against different binaries.

Eventually, the lt binary will be the single entry-point that end-users interact with. It will have various subcommands, so add one for running a script file. The following syntax will be good:

$ lt run <FILE>

where FILE is the path to a .lt script. It will also be nice to follow convention established by other languages, where you can simply pass the script name, e.g. like in python:

$ python foo.py