From 11135be94df8f0063d7a3536437f0830aeeb7b0f Mon Sep 17 00:00:00 2001 From: Danny Yoo Date: Fri, 10 Jun 2011 12:42:40 -0400 Subject: [PATCH] renaming primitives.js since they're not directly the primitives we'll use; I need to adapt them. --- js-assembler/get-runtime.rkt | 10 ++++++-- .../{primitives.js => js-vm-primitives.js} | 0 notes/racket-days-abstract.txt | 23 ++++++++++++------- tests/older-tests/mz-tests/testing.rkt | 2 +- 4 files changed, 24 insertions(+), 11 deletions(-) rename js-assembler/runtime-src/{primitives.js => js-vm-primitives.js} (100%) diff --git a/js-assembler/get-runtime.rkt b/js-assembler/get-runtime.rkt index ed61e5c..02da57b 100644 --- a/js-assembler/get-runtime.rkt +++ b/js-assembler/get-runtime.rkt @@ -31,9 +31,15 @@ (define-runtime-path hashtable.js "runtime-src/jshashtable-2.1_src.js") (define-runtime-path jsnums.js "runtime-src/js-numbers.js") (define-runtime-path link.js "runtime-src/link.js") + +;; from js-vm (define-runtime-path helpers.js "runtime-src/helpers.js") +;; from js-vm (define-runtime-path types.js "runtime-src/types.js") -(define-runtime-path primitives.js "runtime-src/primitives.js") +;; These primitives were coded for the js-vm project, and we'll gradually +;; absorb them in. +(define-runtime-path js-vm-primitives.js "runtime-src/js-vm-primitives.js") + (define-runtime-path runtime.js "runtime-src/runtime.js") @@ -46,7 +52,7 @@ link.js helpers.js types.js - primitives.js + js-vm-primitives.js runtime.js)) diff --git a/js-assembler/runtime-src/primitives.js b/js-assembler/runtime-src/js-vm-primitives.js similarity index 100% rename from js-assembler/runtime-src/primitives.js rename to js-assembler/runtime-src/js-vm-primitives.js diff --git a/notes/racket-days-abstract.txt b/notes/racket-days-abstract.txt index e5887a1..0ecbdf2 100644 --- a/notes/racket-days-abstract.txt +++ b/notes/racket-days-abstract.txt @@ -5,20 +5,23 @@ What is Whalesong? Why would anyone care? - Because it allows Racket programs to be deployed on the web. - Furthermore, Racket programs can access native JavaScript APIs. + * Because it allows Racket programs to be deployed on the web. + + * Furthermore, Racket programs can access native JavaScript APIs. + + * Because my previous attempt at this produced a slower evaluator; + this is much faster. What do you want to show? - I want to show the tool in action, programs that use it, and some - of the internals of how it works. + I want to show the tool in action, programs that use it + - like World programming, FFI - I want to show uses of the FFI. + I want to show performance numbers (which means benchmarks...) - As well as World programming. - - I also want to show performance numbers (which means benchmarks...) + I also want to show some of the internals, to show why the + JavaScript context makes things more complicated. How do you use it? @@ -26,6 +29,10 @@ How do you use it? I have a command line tool that consumes Racket programs and produces standalone JavaScript applications. + I'll be using this as the underlying evaluator for WeScheme + + Why? Performance. + What were the technical advantages of your approach? diff --git a/tests/older-tests/mz-tests/testing.rkt b/tests/older-tests/mz-tests/testing.rkt index 1f83392..c71397e 100644 --- a/tests/older-tests/mz-tests/testing.rkt +++ b/tests/older-tests/mz-tests/testing.rkt @@ -1,4 +1,4 @@ -#lang s-exp "../../lang/base.rkt" +#lang planet dyoo/whalesong (provide test test-values Section record-error arity-test err/rt-test disable