Chromium Code Reviews| Index: runtime/include/dart_api.h |
| =================================================================== |
| --- runtime/include/dart_api.h (revision 32344) |
| +++ runtime/include/dart_api.h (working copy) |
| @@ -876,12 +876,20 @@ |
| DART_EXPORT Dart_Isolate Dart_CurrentIsolate(); |
| /** |
| - * Returns the callback data which was passed to the isolate when it |
| - * was created. |
| + * Returns the callback data associated with the current Isolate. This data was |
| + * passed to the isolate when it was created. |
| */ |
| DART_EXPORT void* Dart_CurrentIsolateData(); |
| /** |
| + * Returns the callback data associated with the specified Isolate. This data |
| + * was passed to the isolate when it was created. |
| + * The embedder is responsible for ensuring that the consistency of this data |
| + * with respect to the lifecycle of an Isolate. |
| + */ |
| +DART_EXPORT void* Dart_IsolateData(Dart_Isolate isolate); |
| + |
| +/** |
| * Returns the debugging name for the current isolate. |
| * |
| * This name is unique to each isolate and should only be used to make |
| @@ -999,6 +1007,9 @@ |
| * mechanism for the delivery of inter-isolate messages. It is the |
| * responsibility of the embedder to call Dart_HandleMessage to |
| * process the message. |
| + * |
|
Ivan Posva
2014/02/07 00:17:46
I don't think we should state this here since we m
siva
2014/02/07 00:35:42
Removed.
On 2014/02/07 00:17:46, Ivan Posva wrote
|
| + * The VM guarantees that the destination isolate 'dest_isolate' will not |
| + * be shutdown while this callback is executed. |
| */ |
| typedef void (*Dart_MessageNotifyCallback)(Dart_Isolate dest_isolate); |