Hide Isolate pointer from embedder

runtime/include/dart_api.h

 /*
  * 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.
  */
 
 #ifndef INCLUDE_DART_API_H_
 #define INCLUDE_DART_API_H_
 
 /** \mainpage Dart Embedding API Reference
@@ skipping 47 matching lines @@
 #else
 #define DART_EXPORT DART_EXTERN_C
 #endif
 #else
 #error Tool chain not supported.
 #endif
 #endif
 
 #include <assert.h>
 
+
+/*
+ * ========
+ * Isolates
+ * ========
+ */
+
+/**
+ * A port is used to send or receive inter-isolate messages. It is also used
+ * to identify an isolate (see Dart_Isolate).
+ */
+typedef int64_t Dart_Port;
+
+
+/**
+ * An isolate is the unit of concurrency in Dart. Each isolate has
+ * its own memory and thread of control. No state is shared between
+ * isolates. Instead, isolates communicate by message passing.
+ *
+ * Each thread keeps track of its current isolate, which is the
+ * isolate which is ready to execute on the current thread. The
+ * current isolate may be ILLEGAL_ISOLATE, in which case no isolate is ready to
+ * execute. Most of the Dart apis require there to be a current
+ * isolate in order to function without error. The current isolate is
+ * set by any call to Dart_CreateIsolate or Dart_EnterIsolate.
+ */
+typedef Dart_Port Dart_Isolate;
+
+/**
+ * ILLEGAL_ISOLATE is an isolate id that is  guaranteed never to be associated
+ * with a valid isolate.
+ */
+#define ILLEGAL_ISOLATE ((Dart_Isolate) 0)

[Ivan Posva, 2015/05/11 04:50:15]

Should probably be DART_ILLEGAL_ISOLATE to reduce naming conflicts. Same for
ILLEGAL_PORT.

[Cutch, 2015/05/12 03:21:28]

Done and done.

+
 /*
  * =======
  * Handles
  * =======
  */
 
 /**
- * An isolate is the unit of concurrency in Dart. Each isolate has
- * its own memory and thread of control. No state is shared between
- * isolates. Instead, isolates communicate by message passing.
- *
- * Each thread keeps track of its current isolate, which is the
- * isolate which is ready to execute on the current thread. The
- * current isolate may be NULL, in which case no isolate is ready to
- * execute. Most of the Dart apis require there to be a current
- * isolate in order to function without error. The current isolate is
- * set by any call to Dart_CreateIsolate or Dart_EnterIsolate.
- */
-typedef struct _Dart_Isolate* Dart_Isolate;
-
-/**
  * An object reference managed by the Dart VM garbage collector.
  *
  * Because the garbage collector may move objects, it is unsafe to
  * refer to objects directly. Instead, we refer to objects through
  * handles, which are known to the garbage collector and updated
  * automatically when the object is moved. Handles should be passed
  * by value (except in cases like out-parameters) and should never be
  * allocated on the heap.
  *
  * Most functions in the Dart Embedding API return a handle. When a
@@ skipping 957 matching lines @@
 DART_EXPORT bool Dart_IsolateMakeRunnable(Dart_Isolate isolate);
 
 
 /*
  * ==================
  * Messages and Ports
  * ==================
  */
 
 /**
- * A port is used to send or receive inter-isolate messages
- */
-typedef int64_t Dart_Port;
-
-/**
  * ILLEGAL_PORT is a port number guaranteed never to be associated with a valid
  * port.
  */
 #define ILLEGAL_PORT ((Dart_Port) 0)
 
 /**
  * A message notification callback.
  *
  * This callback allows the embedder to provide an alternate wakeup
  * mechanism for the delivery of inter-isolate messages.  It is the
@@ skipping 1763 matching lines @@
  * NOTE: If multiple callbacks with the same name are registered, only the
  * last callback registered will be remembered.
  */
 DART_EXPORT void Dart_RegisterRootServiceRequestCallback(
     const char* name,
     Dart_ServiceRequestCallback callback,
     void* user_data);
 
 
 #endif  /* INCLUDE_DART_API_H_ */  /* NOLINT */