wren/test at 95ef1a281459d7c5234306f58b4c0ffd610ccb01 - wren

Files

T

Bob Nystrom 95ef1a2814 feat: rename process module to os and add Platform class with name and isPosix methods

Rename the "process" module to "os" across all source files, documentation, tests, and build configuration. Add a new Platform class to the os module with static methods `name` (returns OS string like "Windows", "Linux", "OS X", "iOS", "Unix", "POSIX", or "Unknown") and `isPosix` (returns bool indicating POSIX compliance). Update all import paths from "process" to "os" in test files and module registrations. Move process.c/h to os.c/h, rename processSetArguments to osSetArguments, and regenerate the os.wren.inc bytecode source. Add documentation pages for the os module and Platform class.

2016-05-21 19:44:17 +00:00

api

docs: rename WrenValue to WrenHandle across embedding docs and C API

2016-05-21 03:55:28 +00:00

benchmark

feat: add wrenGetValueDouble API and benchmark for wrenCall() performance

2015-12-24 01:29:53 +00:00

core

test: add test verifying closures of same code are unequal

2016-03-26 21:22:38 +00:00

feat: add Stdin.isRaw property to query and set terminal raw mode on stdin

2016-05-20 22:19:18 +00:00

language

feat: report undefined variable errors on the line where they are used

2016-03-16 15:00:28 +00:00

limit

fix: add overflow check for jump distance in patchJump and emit error on too much code

2016-02-19 14:57:38 +00:00

README.md

This contains the automated validation suite for the VM and built-in libraries.

benchmark/ - Performance tests. These aren't strictly pass/fail, but let us compare performance both against other languages and against previous builds of Wren itself.
core/ - Tests for the built in core library, mainly methods on the core classes. If a bug is in wren_core.c or wren_value.c, it will most likely break one of these tests.
language/ - Tests of the language itself, its grammar and runtime semantics. If a bug is in wren_compiler.c or wren_vm.c, it will most likely break one of these tests. This includes tests for the syntax for the literal forms of the core classes.
limit/ - Tests for various hardcoded limits. The language doesn't officially specify these limits, but the Wren implementation has them. These tests ensure that limit behavior is well-defined and tested.