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

runtime/platform/thread.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 PLATFORM_THREAD_H_
 #define PLATFORM_THREAD_H_
 
 #include "platform/globals.h"
 
 // Declare the OS-specific types ahead of defining the generic classes.
 #if defined(TARGET_OS_LINUX)
 #include "platform/thread_linux.h"
 #elif defined(TARGET_OS_MACOS)
 #include "platform/thread_macos.h"
 #elif defined(TARGET_OS_WINDOWS)
 #include "platform/thread_win.h"
 #else
 #error Unknown target os.
 #endif
 
 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.

 };
 
 
 class Mutex {
  public:
   Mutex();
   ~Mutex();
 
   void Lock();
   bool TryLock();
@@ skipping 31 matching lines @@
  private:
   MonitorData data_;  // OS-specific data.
 
   DISALLOW_COPY_AND_ASSIGN(Monitor);
 };
 
 }  // namespace dart
 
 
 #endif  // PLATFORM_THREAD_H_