Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(52)

Side by Side Diff: lib/isolate/isolate_frog.dart

Issue 10843007: Cleanup isolate library after frog removal. (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart
Patch Set: Created 8 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
(Empty)
1 // Copyright (c) 2011, the Dart project authors. Please see the AUTHORS file
2 // for details. All rights reserved. Use of this source code is governed by a
3 // BSD-style license that can be found in the LICENSE file.
4
5
6 // Dart isolate's API and implementation for frog. Since dartdocs are generated
7 // using frog, we include here some additional library level comments.
8
9 /**
10 * The `dart:isolate` library defines APIs to spawn and communicate with
11 * isolates.
12 *
13 * All code in dart runs in the context of an isolate. Each isolate has its own
14 * heap, which means that all values in memory, including globals, are available
15 * only to that isolate. The only mechanism available to communicate between
16 * isolates is to pass messages. Messages are sent through ports. This library
17 * defines [ReceivePort] to represent the receiver's end of a communication
18 * channel, and [SendPort] to represent the sender's end.
19 *
20 * All isolates start with an initial receive port, which is set in the
21 * top-level property [port]. This port is used to establish the first
22 * communication between isolates.
23 *
24 * Two APIs are available to spawn a new isolate: [spawnFunction] and
25 * [spawnUri]. [spawnFunction] creates a new isolate that is using the same
26 * source code as the current isolate, [spawnUri] allows spawning an isolate
27 * that was written independently.
28 *
29 * There is currently no way to indicate in the API whether the isolates should
30 * run on the same or different threads. The underlying system will schedule the
31 * isolate were appropriate. In the near future we will add an API to create DOM
32 * isolates. These are isolates that share access to the DOM. All DOM isolates
33 * will run on the UI thread.
34 *
35 * This library is still evolving. New APIs are being added, and some will be
36 * deprecated and removed. In particular, the class [Isolate] will be
37 * deprecated as soon the dartvm has an implementation working for
38 * [spawnFunction] and [spawnUri], and we have an API to spawn DOM isolates.
39 */
40 #library("dart:isolate");
41
42 #import("../uri/uri.dart");
43 #source("isolate_api.dart");
44 #source("frog/compiler_hooks.dart");
45 #source("frog/isolateimpl.dart");
46 #source("frog/ports.dart");
47 #source("frog/messages.dart");
48 #source("timer.dart");
49 #source("timer_hook.dart");
50 #native("frog/natives.js");
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698