Will Speak
04a7c9b5c8
Build Wren for more targets, and run the test suite on both 32 and 64 bit builds. * Update the build config to test both with and without NAN_TAGGING defined. * Updatest `util/test.py` to take the executable suffix as a parameter. This allows the makefile to control which binaries will be tested. Adds a new target to the makefile to be run by travis, this runs the test suite against all of the configurations it builds. * Gcc on some 32 bit platforms was complaining about numeric overflows when -INFINITY was used. Update the logic for converting a double to a string to not explicitly check against the literal values. * Make CI builds run the tests on both 64 _and_ 32 bit builds. * If I limit the number of CPUs on my MBP I can get some of the tests to time out, I'm imagining that the specs of the Travis Macs means that the same is happening there too. Updated the test script to allow an extra few seconds for the test to complete successfully before killing it. * Due to slight differences in accuracy in some computations tests were failing on 32 bit builds. Stop comparing things quite as exactly in the cases where it is causing issues. For some reason 12.34 was refusing to compare equal to itself. Bad show 12.34 :-/. I've also updated the test so it doesn't leak handles even if the assertions fail. * Double-cast from `double` to `uint32_t` to prevent undefined behaviour on overflow of basic integers. This should hopefully prevent 32 bit test failures on Linux. * Move to a version of LibUV with a fix for the 32 bit build error on Travis.
This contains the Wren source code. It is organized like so:
-
optional: the Wren and C source code for the optional modules. These are built in to the VM and can be used even when you embed the VM in your own application. But they are also optional and can be compiled out by setting defines. -
cli: the source code for the command line interface. This is a custom executable that embeds the VM in itself. Code here handles reading command-line, running the REPL, loading modules from disc, etc. -
include: the public header directory for the VM. If you are embedding the VM in your own application, you will add this to your include path. -
module: the source code for the built-in modules that come with the CLI. These modules are written in a mixture of C and Wren and generally use libuv to implement their underlying functionality. -
vm: the source code for the Wren VM itself. Unlike code incliandmodule, this has no dependencies on libuv. If you are embedding the VM in your own application from source, you will compile the files here into your app.