PPAPI: Take PPB_MessageLoop out of Dev

ppapi/c/ppb_message_loop.h

 /* Copyright (c) 2012 The Chromium Authors. All rights reserved.
  * Use of this source code is governed by a BSD-style license that can be
  * found in the LICENSE file.
  */
 
-/* From dev/ppb_message_loop_dev.idl modified Wed Aug 29 12:22:26 2012. */
+/* From ppb_message_loop.idl modified Mon Nov 12 13:33:16 2012. */
 
-#ifndef PPAPI_C_DEV_PPB_MESSAGE_LOOP_DEV_H_
-#define PPAPI_C_DEV_PPB_MESSAGE_LOOP_DEV_H_
+#ifndef PPAPI_C_PPB_MESSAGE_LOOP_H_
+#define PPAPI_C_PPB_MESSAGE_LOOP_H_
 
 #include "ppapi/c/pp_bool.h"
 #include "ppapi/c/pp_completion_callback.h"
 #include "ppapi/c/pp_instance.h"
 #include "ppapi/c/pp_macros.h"
 #include "ppapi/c/pp_resource.h"
 #include "ppapi/c/pp_stdint.h"
 
-#define PPB_MESSAGELOOP_DEV_INTERFACE_0_1 "PPB_MessageLoop(Dev);0.1"
-#define PPB_MESSAGELOOP_DEV_INTERFACE PPB_MESSAGELOOP_DEV_INTERFACE_0_1
+#define PPB_MESSAGELOOP_INTERFACE_1_0 "PPB_MessageLoop;1.0"
+#define PPB_MESSAGELOOP_INTERFACE PPB_MESSAGELOOP_INTERFACE_1_0
 
 /**
  * @file
- * Defines the PPB_MessageLoop_Dev interface.
+ * Defines the PPB_MessageLoop interface.
  */
 
 
 /**
  * @addtogroup Interfaces
  * @{
  */
 /**
  * A message loop allows PPAPI calls to be issued on a thread. You may not
  * issue any API calls on a thread without creating a message loop. It also
@@ skipping 101 matching lines @@
  *
  *   pp::CompletionCallback callback = factory_.NewOptionalCallback(...);
  *   int32_t result = message_loop.PostWork(callback);
  *   if (result != PP_OK_COMPLETIONPENDING)
  *     callback.Run(result);
  *
  * This will run the callback with an error value, and assumes that the
  * implementation of your callback checks the "result" argument and returns
  * immediately on error.
  */
-struct PPB_MessageLoop_Dev_0_1 {
+struct PPB_MessageLoop_1_0 {
   /**
    * Creates a message loop resource.
    *
    * This may be called from any thread. After your thread starts but before
    * issuing any other PPAPI calls on it, you must associate it with a message
    * loop by calling AttachToCurrentThread.
    */
   PP_Resource (*Create)(PP_Instance instance);
   /**
    * Returns a resource identifying the message loop for the main thread. The
@@ skipping 97 matching lines @@
    *   - PP_ERROR_FAILED: The message loop has been destroyed.
    */
   int32_t (*PostWork)(PP_Resource message_loop,
                       struct PP_CompletionCallback callback,
                       int64_t delay_ms);
   /**
    * Posts a quit message to the given message loop's work queue. Work posted
    * before that point will be processed before quitting.
    *
    * This may be called on the message loop registered for the current thread,
-   * or it may be called on the message loop registered for another thread.
+   * or it may be called on the message loop registered for another thread. It
+   * is an error to attempt to PostQuit() the main thread loop.
    *
    * @param should_destroy Marks the message loop as being in a destroyed state
    * and prevents further posting of messages.
    *
    * If you quit a message loop without setting should_destroy, it will still
    * be attached to the thread and you can still run it again by calling Run()
    * again. If you destroy it, it will be detached from the current thread.
    *
    * @return
    *   - PP_OK: The request to quit was successfully posted.
    *   - PP_ERROR_BADRESOURCE: The message loop was invalid.
    *   - PP_ERROR_WRONG_THREAD: You are attempting to quit the main thread.
    *     The main thread's message loop is managed by the system and can't be
    *     quit.
    */
   int32_t (*PostQuit)(PP_Resource message_loop, PP_Bool should_destroy);
 };
 
-typedef struct PPB_MessageLoop_Dev_0_1 PPB_MessageLoop_Dev;
+typedef struct PPB_MessageLoop_1_0 PPB_MessageLoop;
 /**
  * @}
  */
 
-#endif  /* PPAPI_C_DEV_PPB_MESSAGE_LOOP_DEV_H_ */
+#endif  /* PPAPI_C_PPB_MESSAGE_LOOP_H_ */