.. |
coersing
|
changing the constant back
|
2011-07-27 15:55:49 -04:00 |
conform
|
trying to trace why conform is failing
|
2011-05-18 14:11:12 -04:00 |
earley
|
removing dependency on types
|
2011-07-06 17:00:42 -04:00 |
module-test
|
continuing to work on package
|
2011-05-23 12:30:36 -04:00 |
more-tests
|
oops, forgot to add in the hello-bf example
|
2011-07-27 13:07:09 -04:00 |
older-tests
|
renaming primitives.js since they're not directly the primitives we'll use; I need to adapt them.
|
2011-06-10 12:42:40 -04:00 |
browser-evaluate.rkt
|
browser-harness.rkt to make it easier to run the tests
|
2011-06-30 15:59:46 -04:00 |
browser-harness.rkt
|
cleanup
|
2011-07-10 19:17:13 -04:00 |
run-more-tests.rkt
|
moving tests
|
2011-07-22 18:47:03 -04:00 |
test-all.rkt
|
tests adjusted to dodge what appears to be a bug in zo-parse regarding splicing begin at a non-module toplevel. This is something that we'll probably not hit in module contexts. Hopefully.
|
2011-07-22 12:01:09 -04:00 |
test-assemble.rkt
|
Renaming TestAndBranch to TestAndJump, since I want to have a dedicated branch statement that reuses JavaScript's native if
|
2011-07-16 17:59:15 -04:00 |
test-browser-evaluate.rkt
|
rewriting the splicing begins to lets to dodge the bug in the 5.1.2 parser
|
2011-07-22 11:57:29 -04:00 |
test-compiler-2.rkt
|
rewriting the splicing begins to lets to dodge the bug in the 5.1.2 parser
|
2011-07-22 11:57:29 -04:00 |
test-compiler.rkt
|
rewriting the splicing begins to lets to dodge the bug in the 5.1.2 parser
|
2011-07-22 11:57:29 -04:00 |
test-conform-browser.rkt
|
figured out the bug. Silly function taking in more arguments than it needs.
|
2011-06-09 11:55:17 -04:00 |
test-conform.rkt
|
moving tests to separate directory
|
2011-05-20 10:48:44 -04:00 |
test-earley-browser.rkt
|
figured out the bug. Silly function taking in more arguments than it needs.
|
2011-06-09 11:55:17 -04:00 |
test-earley.rkt
|
need to figure out why it takes so long to parse bytecode.
|
2011-05-20 11:23:28 -04:00 |
test-get-dependencies.rkt
|
need to trace why the browser tests are suddenly failing
|
2011-06-08 14:37:04 -04:00 |
test-helpers.rkt
|
Moved compiler-related stuff to compiler subdirectory
|
2011-05-26 19:46:49 -04:00 |
test-package.rkt
|
tests adjusted to dodge what appears to be a bug in zo-parse regarding splicing begin at a non-module toplevel. This is something that we'll probably not hit in module contexts. Hopefully.
|
2011-07-22 12:01:09 -04:00 |
test-parse-bytecode-on-collects.rkt
|
failures saved as list rather than exceptions, since memory usage seemed a lot higher than expected.
|
2011-06-05 16:13:18 -04:00 |
test-parse-bytecode.rkt
|
rewriting the splicing begins to lets to dodge the bug in the 5.1.2 parser
|
2011-07-22 11:57:29 -04:00 |
test-parse.rkt
|
toplevel refs remember if they need to be checked
|
2011-07-22 11:15:10 -04:00 |
test-simulator.rkt
|
Renaming TestAndBranch to TestAndJump, since I want to have a dedicated branch statement that reuses JavaScript's native if
|
2011-07-16 17:59:15 -04:00 |