Pepper: Autogenerate thunk for PPB_TrueTypeFont.

ppapi/api/ppb_gamepad.idl

Index: ppapi/api/ppb_gamepad.idl
diff --git a/ppapi/api/ppb_gamepad.idl b/ppapi/api/ppb_gamepad.idl
index 6403e345b08adc5e96170a059b01b1aca531b01e..2c7a9a1f88f420d5628db636f05d687ef1a4f1a7 100644
--- a/ppapi/api/ppb_gamepad.idl
+++ b/ppapi/api/ppb_gamepad.idl
@@ -85,11 +85,12 @@ struct PP_GamepadsSampleData {
  * The <code>PPB_Gamepad</code> interface allows retrieving data from
  * gamepad/joystick devices that are connected to the system.
  */
-[version=1.0, macro="PPB_GAMEPAD_INTERFACE", singleton_resource]
+[version=1.0, macro="PPB_GAMEPAD_INTERFACE"]
 interface PPB_Gamepad {
   /**
    * Samples the current state of the connected gamepads.
    */
+  [singleton]

[yzshen1, 2013/04/10 17:00:48]

I understand that sometimes per-function annotation is necessary. However, I
think for most of interfaces, their methods are either all singleton or all
non-singleton. In that case, it would be more concise to do an interface-level
annotation. Does that make sense? 

   void Sample(
       [in] PP_Instance instance,
       [out] PP_GamepadsSampleData data);