[PPAPI] Added PP_VARTYPE_RESOURCE as a PP_VarType enum value.

ppapi/proxy/raw_var_data.cc

Index: ppapi/proxy/raw_var_data.cc
diff --git a/ppapi/proxy/raw_var_data.cc b/ppapi/proxy/raw_var_data.cc
index a550c3fca052892976c32288a6b807fa4cff211f..6379c7a2aa8c7913442c0771945bf4fb2948fb18 100644
--- a/ppapi/proxy/raw_var_data.cc
+++ b/ppapi/proxy/raw_var_data.cc
@@ -240,6 +240,13 @@ RawVarData* RawVarData::Create(PP_VarType type) {
       return new ArrayRawVarData();
     case PP_VARTYPE_DICTIONARY:
       return new DictionaryRawVarData();
+    case PP_VARTYPE_RESOURCE:
+      // TODO(mgiuca): Add ResourceRawVarData. (http://crbug.com/177017)
+      // This path will be reached if a NaCl module attempts to pass a
+      // PP_VARTYPE_RESOURCE in a message.
+      NOTIMPLEMENTED();
+      CHECK(false) << "Serializing PP_VARTYPE_RESOURCE is not supported.";

[raymes, 2013/09/11 22:52:29]

I realise that you are going to be changing this soon, but I think it might be
better to maintain the existing behavior here and just have a NOTREACHED() here.

[Matt Giuca, 2013/09/12 07:08:24]

OK, fair enough.

That will result in a NULL pointer dereference in the plugin module on the
release build. But I suppose that a) that is equivalent to the current behaviour
anyway, if the user decides to set a var's type to 100, and b) that is no worse
than a checkfail (just harder to diagnose).

+      return NULL;
   }
   NOTREACHED();
   return NULL;