Fix functionExpression() incorrectly prohibiting the use of an identifier as in:

var f = function foo() { ... }

As specified in http://www.ecma-international.org/ecma-262/5.1/#sec-13 this syntax is valid (the identifier being optional).
Move the call to "execute" to a method that can be overridden. Needed to allow running the JS code in an event loop thread in Nodyn.
Arrange for continue statements inside a switch block not to fall through to next case.
Add unit test for continue fix.
Merge pull request #125 from malaporte/fix-continue-in-switch

Fix continue in switch statement
Add jasmine spec test to validate fix.
Merge pull request #123 from malaporte/fix-function-expression-with-identifier

Fix functionExpression() incorrectly prohibiting the use of an identifier
Merge pull request #124 from malaporte/fix-event-loop-in-nodyn

Move the call to "execute" to a method that can be overridden.
Make Runner subclassable and Arguments configurable
Actually expose the DynJS runtime from the dynjs builtin.
Make Main.java initializeRuntime in run()
Remove shadow debug output
Rev AEsh
Make a bunch of stuff enumerable:true in the GlobalObject.
Display better token information for unprintable tokens.
Improve ObjectEnvironmentRecord so that a bare property referenced upon
the global object follows normal property-accessor rules (including using
getters, if defined).

For instance, if the global object is available as 'g':

  Object.defineProperty( g, 'foo', { get: function(){ return 42; } } )

Then accessing bare property 'foo' should return 42.

  > foo
  42

Previously, the ObjectedEnvironmentRecord purely return the value: field
of the PropertyDescriptor, instead of using getters.
Begin separating CompilationContext from ExecutionContext.
Enable Runner to take a JSProgram.
Special-case for: delete javaMap.key // delete javaMap[key]
  -- note interpreted mode only so far.
Fix signature for change with CompilationContext.