Use macros to define pepper interfaces

ppapi/proxy/plugin_dispatcher_unittest.cc

Index: ppapi/proxy/plugin_dispatcher_unittest.cc
diff --git a/ppapi/proxy/plugin_dispatcher_unittest.cc b/ppapi/proxy/plugin_dispatcher_unittest.cc
index 56f563bd9309ff6d9439f6e512c143655ac5222a..8a32026a036986bf8864c36ebf2e22db2dd8f913 100644
--- a/ppapi/proxy/plugin_dispatcher_unittest.cc
+++ b/ppapi/proxy/plugin_dispatcher_unittest.cc
@@ -53,7 +53,7 @@ class PluginDispatcherTest : public PluginProxyTest {
   PluginDispatcherTest() {}
 
   bool HasTargetProxy(InterfaceID id) {
-    return !!plugin_dispatcher()->target_proxies_[id].get();
+    return !!plugin_dispatcher()->proxies_[id].get();

[noelallen_use_chromium, 2011/09/07 21:16:57]

If this is the normal way to do a pointer check, we should probably update the
style guide.

   }
 };
 
@@ -64,11 +64,6 @@ TEST_F(PluginDispatcherTest, SupportsInterface) {
   // Sending a request for a random interface should fail.
   EXPECT_FALSE(SupportsInterface("Random interface"));
 
-  // Sending a request for a PPB interface should fail even though we've
-  // registered it as existing in the GetInterface function (the plugin proxy
-  // should only respond to PPP interfaces when asked if it supports them).
-  EXPECT_FALSE(SupportsInterface(PPB_AUDIO_INTERFACE));
-
   // Sending a request for a supported PPP interface should succeed.
   EXPECT_TRUE(SupportsInterface(PPP_INSTANCE_INTERFACE));
 }