Add PPAPI_BEGIN_MESSAGE_MAP and PPAPI_END_MESSAGE_MAP to be used when dispatching IPCs using PPAPI_…

content/browser/renderer_host/pepper/pepper_message_filter.cc

Index: content/browser/renderer_host/pepper/pepper_message_filter.cc
===================================================================
--- content/browser/renderer_host/pepper/pepper_message_filter.cc	(revision 270145)
+++ content/browser/renderer_host/pepper/pepper_message_filter.cc	(working copy)
@@ -20,11 +20,9 @@
                                             bool* message_was_ok) {
   bool handled = true;
   IPC_BEGIN_MESSAGE_MAP_EX(PepperMessageFilter, msg, *message_was_ok)

[Tom Sepez, 2014/05/13 20:03:47]

Did you mean to convert these to PPAI_BEGIN_MESSAGE_MAP as well?

[jam, 2014/05/13 20:19:39]

these ones still use IPC_MESSAGE_HANDLER, so that's why i didn't change them. i
just fixed the indentation to match our convention

[dmichael (off chromium), 2014/05/14 15:40:06]

Note, this is one of clang-format's idiosyncrasies. I haven't turned on
presubmit checks to enforce it yet, because I'm not done converting all of
Pepper over. It's easy enough for me to change back, so I don't mind either way.
I care little enough about the difference here that in the long run I was
planning to accept the slightly less nice way to get the benefit of
clang-format. I can't think of any good way to make clang-format understand
this, unless we teach it about our IPC macros.

-  // X509 certificate messages.
-  IPC_MESSAGE_HANDLER(PpapiHostMsg_PPBX509Certificate_ParseDER,
-                      OnX509CertificateParseDER);
-
-  IPC_MESSAGE_UNHANDLED(handled = false)
+    IPC_MESSAGE_HANDLER(PpapiHostMsg_PPBX509Certificate_ParseDER,
+                        OnX509CertificateParseDER)
+    IPC_MESSAGE_UNHANDLED(handled = false)
   IPC_END_MESSAGE_MAP_EX()
   return handled;
 }