TypeScript

The TypeScript port of the Lysithea VM.

Examples

The core code is under ./src folder with ported examples under the ./examples folder.

$ npm install

$ npm run perfTest
$ npm run stdLib
$ npm run diagTree
$ npm run readmeExampleErrors
$ npm run readmeExampleScopes

Build

The TypeScript can be built for JavaScript.

$ npm run build

Code

Currently the code is written with a Lisp like syntax. It should not be assumed that it is Lisp or that it supports all the things that Lisp would support. Lisp was chosen for it's ease of parsing and tokenising.

(function main ()
    (print "Result: " (+ 5 12))
)

(main)

This will push the 5 and 12 to the stack and then run the + operators, then push "print" to the stack and run the call opcode. As for "print" will do it up to environment that the virtual machine is running in. Ideally however the final result would print to a console Result: 17.

Simple Program

To make use of Lysithea in a TS project you can either copy of the contents of the src folder into your project and make changes to it as you see fit. Or get a copy of it from npm.

import { VirtualMachine, Assembler, LibraryType, addToScope } from 'lysithea-vm';

// The assembler is responsible for turning script text into an executable script.
const assembler = new Assembler();

// By default only basic math operators will be understood, this adds all the
// standard libraries to the assembler. You can also add your own functions and values.
addToScope(assembler.builtinScope, LibraryType.all);

// Now we can assemble a script.
// The first argument lets it know the source of the text for throwing errors in a specific file.
// The second is the script text itself.
const script = assembler.parseFromText('CodeExample', '(print "Result: " (+ 5 12))');

// To actually execute a script it needs a virtual machine.
// The VM actually holds all the information about a current execution such as the current
// call stack and code location.

// The argument indicates how big the stack and call stack can be.
// The call stack limits how many functions can be called from inside each other.
// The stack itself limits how many arguments can be used to call a function.
// These are two independent stacks.
const vm = new VirtualMachine(8);

// Internally the VM runs on a loop and you can either ask it to run until it's finished
vm.execute(script);
//
// OR
//

// You can control the loop yourself, you may want to do this when you want to do more advanced things
// like control how many steps can be executed at once for a long running process or by some other limiting factor.
vm.changeToScript(script);
vm.running = true;
vm.paused = false;
while (vm.running && !vm.paused)
{
    vm.step();
}

// Regardless of which execution path chosen it should log to the console
// Result: 17

This example skips worrying about catching any assembler errors or runtime errors.

Adding Error Handling

Let's say you do want to do some error handling.

There's 2 types of errors:

AssemblerError: When parsing the tokens do things make reasonable sense, have you given the right number of arguments to certain keywords (if/unless), have you attempted to redefine a constant, is there an unexpected bracket, etc.

This will contain a trace location as to where in the script this happened.

VirtualMachineError: These are run time errors that weren't able to be caught by the assembler.

This will be things like functions not being found, labels not found, etc.

This will contain a stackTrace as a list of string locations at to where this occurred in the script based on function calls.

import {
    VirtualMachine,
    Assembler,
    addToScope,
    LibraryType,
    VirtualMachineError,
    AssemblerError } from '../src/index';

const assembler = new Assembler();
addToScope(assembler.builtinScope, LibraryType.all);

const vm = new VirtualMachine(8);

function tryExecute(vm: VirtualMachine, sourceName: string, text: string)
{
    try
    {
        const script = assembler.parseFromText(sourceName, text);
        vm.execute(script);

        return true;
    }
    catch (err)
    {
        if (err instanceof VirtualMachineError)
        {
            const stackTrace = err.stackTrace.join('\n');
            console.error(`Runtime Error: ${err.message}\n${stackTrace}`);
        }
        else if (err instanceof AssemblerError)
        {
            console.error(`Assembler Error: ${err.message}\n${err.trace}`);
        }
        else
        {
            console.error('Unexpected error: ', err);
        }
        return false;
    }
}

const runtimeErrorExample = `
    (define num1 18)
    (define num2 3)
    (print "Div: " (/ num1 num2))
    (print "Mul: " (* num1 num3))`;

if (!tryExecute(vm, 'RuntimeErrorExample', runtimeErrorExample))
{
    console.log('Oh no!');
}

/* Outputs
Div: 6
Runtime Error: global:12: Unable to get variable: num3
RuntimeErrorExample:5:28
4:     (print "Div: " (/ num1 num2))
5:     (print "Mul: " (* num1 num3))
                             ^----^

Oh no!
*/

const unexpectedBracketExample = `
    (define num1 18)
    (define num2 3))
    (print "Div: " (/ num1 num2))
    (print "Mul: " (* num1 num3))`;

if (!tryExecute(vm, 'UnexpectedBracket', unexpectedBracketExample))
{
    console.log('Oh no!');
}

/* Outputs
Assembler Error: 2:17 -> 3:0: ): 2:17 -> 3:0: ): Unexpected )
UnexpectedBracket:3:18
2:     (define num1 18)
3:     (define num2 3))
                   ^---^
4:     (print "Div: " (/ num1 num2))

Oh no!
*/

const assemblerErrorExample = `
    (const num1 18)
    (define num1 "Redefined")
    (define num2 3)
    (print "Div: " (/ num1 num2))
    (print "Mul: " (* num1 num3))`;

if (!tryExecute(vm, 'AssemblerErrorExample', assemblerErrorExample))
{
    console.log('Oh no!');
}

/* Outputs
Assembler Error: 2:12 -> 2:17: num1: Attempting to define a constant: num1: AssemblerErrorExample:3:13
2:     (const num1 18)
3:     (define num1 "Redefined")
              ^----^
4:     (define num2 3)

Oh no!
*/

Adding Extra Functionality

So by default the VM only supports basic arithmetic (+, -, *, /) and comparisons (<, >, >=, <=, ==, !=). The standard library gives you some more functionality around manipulating some of the builtin types, like strings, lists and maps but that still doesn't let you do much.

So in general you'll be adding extra functionality to actually do something for your specific program.

There's two main ways of doing this, adding extra functions and values to the assembler and adding extra functions and values to the virtual machine.

The main difference being that when done at the assembler stage it lets it inline calls to those functions increasing performance and it means that even if the virtual machine in unaware of those function it won't need to, unless you want to dynamically find those functions.

Additionally this extra functionality can be grouped together into a scope which can then be combined with the assembler or virtual machines scope. Or you can define individual values.

Example

In this example the isDefined function checks if there is a variable with that name found anywhere in the accessible scope; either current scope or parent scope up to global but not the builtin scope to the script!

There is also an isBuiltin function which checks if there is a builtin constant with that name. This only works for global constants, as function level constants are not stored anywhere outside of the inlining.

Here is a somewhat lengthy example of different ways of adding extra functionality. Property error handling has been left out for brevity.

import {
    VirtualMachine,
    Assembler,
    addToScope,
    LibraryType,
    ObjectValueMap,
    BuiltinFunctionValue,
    ObjectValue,
    Scope,
    NumberValue,
    BuiltinFunctionCallback } from '../src/index';

const randomInt: BuiltinFunctionCallback = (vm, args) =>
{
    const min = args.getNumber(0);
    const max = args.getNumber(1);
    const diff = max - min + 1;
    vm.pushStackNumber(Math.floor(Math.random() * diff) + min);
};

const randomBool: BuiltinFunctionCallback = (vm, args) =>
{
    vm.pushStackBool(Math.random() > 0.5);
};

const randomNumber: BuiltinFunctionCallback = (vm, args) =>
{
    vm.pushStackNumber(Math.random());
};

// Create an object that contains will contain functions, however this is just
// a way to group things under a single object, kind of like a namespace, but it's only an object.
const randFuncs: ObjectValueMap =
{
    int: new BuiltinFunctionValue(randomInt, 'random.int'),
    bool: new BuiltinFunctionValue(randomBool, 'random.bool')
};
const randomObj = new ObjectValue(randFuncs);

// Create a scope to store all the values.
const randomScope = new Scope();

// Set the object onto the scope
randomScope.tryDefine('random', randomObj);

// You can also set a function directly onto the scope
randomScope.tryDefineFunc('randomNumber', randomNumber);

// You can define a simple value as well.
randomScope.tryDefine('seed', new NumberValue(1234));

// The actual code that will be used.
const scriptText = `
    (print 'Int 0-100 ' (random.int 0 100))
    (print 'Bool ' (random.bool))
    (print 'Random Value ' (randomNumber))
    (print 'Seed ' seed)
    (print 'Seed in dynamic scope? ' (isDefined 'seed'))
    (print 'Seed in builtin scope? ' (isBuiltin 'seed'))
`;

// This does not make use of the randomScope object and instead directly adds the
// values onto the assembler.
function noScope()
{
    const assembler = new Assembler();
    assembler.builtinScope.tryDefine('random', randomObj);
    assembler.builtinScope.tryDefineFunc('randomNumber', randomNumber);
    assembler.builtinScope.tryDefine('seed', new NumberValue(1234));
    addToScope(assembler.builtinScope, LibraryType.all);

    const vm = new VirtualMachine(8);

    const script = assembler.parseFromText('noScopeScript', scriptText);
    vm.execute(script);
}

// Makes use of the randomScope to simplify adding values to the assemblers known values.
function assemblerScope()
{
    const assembler = new Assembler();
    assembler.builtinScope.combineScope(randomScope);
    addToScope(assembler.builtinScope, LibraryType.all);

    const vm = new VirtualMachine(8);

    const script = assembler.parseFromText('assemblerScopeScript', scriptText);
    vm.execute(script);
}

// Makes use of the randomScope but adds the values to just the virtual machine.
function vmScope()
{
    const assembler = new Assembler();
    addToScope(assembler.builtinScope, LibraryType.all);

    const vm = new VirtualMachine(8);
    vm.globalScope.combineScope(randomScope);

    const script = assembler.parseFromText('vmScopeScript', scriptText);
    vm.execute(script);
}

console.log('No Scope');
noScope();

/* Output
No Scope
Int 0-100 50
Bool false
Random Value 0.9965207443661974
Seed 1234
Seed in dynamic scope? false
Seed in builtin scope? true
*/

console.log('\nAssembler Scope');
assemblerScope();

/* Output
Assembler Scope
Int 0-100 81
Bool false
Random Value 0.2369186667119021
Seed 1234
Seed in dynamic scope? false
Seed in builtin scope? true
*/

console.log('\nVirtual Machine Scope');
vmScope();

/* Output
Virtual Machine Scope
Int 0-100 41
Bool false
Random Value 0.21756404325237733
Seed 1234
Seed in dynamic scope? true
Seed in builtin scope? false
*/

Detailed Comparison of Scope Usage

Here is how the code looks like after being assembled with the noScope and assemblerScope, basically if the assembler is able to directly find the values it needs.

As you can see there are fewer operators needed as there is less looking up of values at run time.

Both the standard library call to print is inlined as well as the calls to the random object and it's values random.int and random.bool and the value of seed is inlined as well.

Note! This does mean that anything known at assembler time is baked in and changing those values at run time will not be seen! You cannot change the value of seed for example if it is known at assembler time. To do that sort of thing you can simply leave it out of the assembler's builtinScope.

Both these tables leave out the operators for calling isDefined and isBuiltin for brevity and they are the same between both tables.

| Operator | Argument | Current Stack | | -------- | -------- | --- | | push | "Int 0-100 " | "Int 0-100 " | | push | 0 | "Int 0-100 ", 0 | | push | 100 | "Int 0-100", 0, 100 | | callDirect | [random.int, 2] | "Int 0-100 ", 64 (some random number) | | callDirect | [print, 2] | empty | | push | "Bool " | "Bool " | | callDirect | [random.bool, 0] | "Bool ", false (some random bool) | | callDirect | [print, 2] | empty | | push | "Random Value " | "Random Value " | | callDirect | [randomNumber, 0] | "Random Value ", 0.1234 (some random number) | | callDirect | [print, 2] | empty | | push | "Seed " | "Seed " | | push | 1234 | "Seed ", 1234 | | callDirect | [print, 2] | empty |

Here is what the vmScope example code looks like, it contains get and getProperty calls to find the random object and then find function before it can call it. This does not affect the assemblers ability to inline calls to the print function from the standard library.

Note! This does give you the ability to load up functions dynamically, change values at run time and the script doesn't need to be assembled again. This mostly has an impact on performance which may or may not be an issue for your situation.

| Operator | Argument | Current Stack | | -------- | -------- | --- | | push | "Int 0-100 " | "Int 0-100 " | | push | 0 | "Int 0-100 ", 0 | | push | 100 | "Int 0-100 ", 0, 100 | | get | random | "Int 0-100 ", 0, 100, {object: random} | | getProperty | int | "Int 0-100 ", 0, 100, {function: random.int} | | call | 2 | "Int 0-100 ", 32 (some random number) | | callDirect | [print, 2] | empty | | push | "Bool " | "Bool " | | get | random | "Bool ", {object: random} | | getProperty | bool | "Bool ", {function: random.bool} | | call | 0 | "Bool ", true (a random bool) | | callDirect | [print, 2] | empty | | push | Random Value | "Random Value " | | get | randomNumber | "Random Value ", {function: randomNumber} | | call | 0 | "Random Value ", 0.543 (some random number) | | callDirect | [print, 2] | empty | | push | "Seed " | "Seed " | | get | seed | "Seed", 1234 | | callDirect | [print, 2] | empty |

More details

For more details, see the main repositories documentation.

License

MIT

Author

Alan Lawrey 2024