Change the thread interface in runtime/platform and use it starting all threads

runtime/platform/thread.h

Index: runtime/platform/thread.h
diff --git a/runtime/platform/thread.h b/runtime/platform/thread.h
index 0eb8da13b2b502412cc21ac54951290785a4a64e..5c04d1e5c077352c186541e2b44345c71d44b3c6 100644
--- a/runtime/platform/thread.h
+++ b/runtime/platform/thread.h
@@ -22,17 +22,10 @@ namespace dart {
 
 class Thread {
  public:
-  // Function to be called on thread start.
   typedef void (*ThreadStartFunction) (uword parameter);
 
-  // TODO(iposva): Define the proper interface for spawning and killing threads.
-  Thread(ThreadStartFunction function, uword parameters);
-  ~Thread();
-
- private:
-  ThreadData data_;
-
-  DISALLOW_COPY_AND_ASSIGN(Thread);
+  // Start a thread running the specified function.
+  static void Start(ThreadStartFunction function, uword parameters);

[siva, 2012/01/24 02:26:05]

Now that you are using threads formally in a thread pool and a server process
setting does it make sense to return an error from this function instead of the
Fatal death on error?

[Søren Gjesse, 2012/01/24 12:07:55]

Added a return code here. It's an int which holds the system specific error
code. Zero is success. For now all callers of Thread::Start has the fatal death
on error.

 };