From 5ebf716f69e08c9cf5a77a6d831a20806bd96ce1 Mon Sep 17 00:00:00 2001 From: Danny Yoo Date: Fri, 22 Jul 2011 13:56:25 -0400 Subject: [PATCH] light editing --- notes/racket-days-abstract.txt | 45 +++++++++++++++++----------------- 1 file changed, 22 insertions(+), 23 deletions(-) diff --git a/notes/racket-days-abstract.txt b/notes/racket-days-abstract.txt index d56011f..e714234 100644 --- a/notes/racket-days-abstract.txt +++ b/notes/racket-days-abstract.txt @@ -56,58 +56,58 @@ What needs to be done next? The story for the presentation: -What's Whalesong? It's a Racket to JavaScript compiler. Here's an -example of it in action. - -(Compile a very simple program to a web page, a computation, then show -that it's effective.) -Whalesong will be used to support World programming for the web. For -example, we can support simple animations, as you'd expect: +What's Whalesong? It's a Racket to JavaScript compiler. Whalesong +will be used to support World programming for the web. It will be the +evaluator for the upcoming versions of Moby Scheme, as well as +WeScheme. + + +We can support simple animations, as you'd expect: (Show a world program: the falling rain drops program.) - -But we can also do programs that have interactivity, such as: +We can do programs that have interactivity, such as: (Show another world program: pacman.) - A core idea behind Whalesong is to reuse Racket's infrastructure as -much as possible. I'm not a compiler person. I can piggiback on -Matthew's work, though. Whalesong reuses the bytecode compiler, and -translates the bytecode to JavaScript. I really am reusing the -linguistic features of Racket. For example, let's look at the -less-than-impressive program output below. +much as possible. I'm not a compiler person, so I cheat, by +piggibacking on Matthew's work. Whalesong reuses the bytecode +compiler, and translates the bytecode to JavaScript. + +I really am reusing the linguistic features of Racket. For example, +let's look at the less-than-impressive program output below. (Show the hello world program) -This is not too impressive. But let's look at the source code. +This is trivial, right? Let's look at the source code. -(Show the BF program.) +(Reveal that the program was written in BF) -Yeah. So we really are using Racket's underlying language features to -handle things like macro expansion. +Yes, this is unholy, but it works. We really are using Racket's +underlying language features to handle reading, macro expansion, and +optimization. Because we're on the web, we may even want to use functions that we've -written in Racket as a part of regular web pages. Whalesong lets you +written in Racket as a part of regular web pages. Whalesong lets us do this. (Show the factorial example, and how it can be used by external -JavaScript on a web page). +JavaScript on a web page.) There's quite a bit that's missing: we don't yet have all of the primitives necessary to compile racket/base, so all Whalesong programs -have to be in a language that ultimately bottoms to (planet +currently have to be in a language that ultimately bottoms to (planet dyoo/whalesong/lang/base). I'm going to get a release out in the following month, and the new @@ -115,5 +115,4 @@ versions of Moby Scheme for Smartphones, as well as the WeScheme environment, will be using the underlying evaluator of Whalesong. - If you're interested, please talk to me during the break. Thanks!