Add support for capturing and changing the current isolate in the closure wrapper.

lib/isolate/isolate_leg.dart

 // Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 
 /**
  * The `dart:isolate` library defines APIs to spawn and communicate with
  * isolates.
  *
  * All code in dart runs in the context of an isolate. Each isolate has its own
@@ skipping 25 matching lines @@
  */
 #library("dart:isolate");
 
 //#import("../uri/uri.dart");
 #import("../../frog/leg/lib/uri_toremove.dart");
 #source("isolate_api.dart");
 #source("frog/compiler_hooks.dart");
 #source("frog/isolateimpl.dart");
 #source("frog/ports.dart");
 #source("frog/messages.dart");
+
+/**
+ * These methods are called by the compiler to support switching

[ahe, 2012/03/16 14:03:16]

A documentation comment only applies to one element.

[ngeoffray, 2012/03/19 10:29:58]

Done.

+ * between isolates when we get a callback from the DOM.
+ */
+void _callInIsolate(IsolateContext isolate, Function function) {

[ahe, 2012/03/16 14:03:16]

I would rather have these methods in js_helper.

[ngeoffray, 2012/03/19 10:29:58]

I agree, and maybe long-term that's what will happen. However, these methods
currently use isolate library specific methods that I'm not sure we want to leak
in the leg compiler.

+  isolate.eval(function);
+  _globalState.topEventLoop.run();
+}
+
+void _currentIsolate() => _globalState.currentContext;