Add PPAPI style enums to V2 IDL parser

tools/idl_parser/test_parser/enum_ppapi.idl

Index: tools/idl_parser/test_parser/enum_ppapi.idl
diff --git a/tools/idl_parser/test_parser/enum_web.idl b/tools/idl_parser/test_parser/enum_ppapi.idl
similarity index 77%
copy from tools/idl_parser/test_parser/enum_web.idl
copy to tools/idl_parser/test_parser/enum_ppapi.idl
index 233410c5d5dc8bcc6286db23f7c3d35c2a0d8b85..c58126ccbca676eb50f9e49b642c36e6ebc557a1 100644
--- a/tools/idl_parser/test_parser/enum_web.idl
+++ b/tools/idl_parser/test_parser/enum_ppapi.idl
@@ -37,19 +37,19 @@ symatics should exist.  This is an exact match.
 */
 enum MealType1 {
   /* BUILD EnumItem (rice) */
-  "rice",
+  rice,
   /* BUILD EnumItem (noodles) */
-  "noodles",
+  noodles,
   /* BUILD EnumItem(other) */
-  "other"
+  other
 };
 
 /* BUILD Error(Enum missing name.) */
 /* ERROR Enum missing name. */
 enum {
-  "rice",
-  "noodles",
-  "other"
+  rice,
+  noodles,
+  other,
 };
 
 /* TREE
@@ -60,60 +60,60 @@ enum {
 */
 enum MealType2 {
   /* BUILD EnumItem(rice) */
-  "rice",
+  rice,
   /* BUILD EnumItem(noodles) */
-  "noodles",
+  noodles = 1,
   /* BUILD EnumItem(other) */
-  "other"
+  other
 };
 
-/* BUILD Error(Unexpected string "noodles" after string "rice".) */
-/* ERROR Unexpected string "noodles" after string "rice". */
+/* BUILD Error(Unexpected identifier "noodles" after identifier "rice".) */
+/* ERROR Unexpected identifier "noodles" after identifier "rice". */
 enum MissingComma {
-  "rice"
-  "noodles",
-  "other"
+  rice
+  noodles,
+  other
 };
 
 /* BUILD Error(Trailing comma in block.) */
 /* ERROR Trailing comma in block. */
 enum TrailingComma {
-  "rice",
-  "noodles",
-  "other",
+  rice,
+  noodles,
+  other,
 };
 
 /* BUILD Error(Unexpected "," after ",".) */
 /* ERROR Unexpected "," after ",". */
 enum ExtraComma {
-  "rice",
-  "noodles",
-  ,"other",
+  rice,
+  noodles,
+  ,other,
 };
 
 /* BUILD Error(Unexpected keyword "interface" after "{".) */
 /* ERROR Unexpected keyword "interface" after "{". */
 enum ExtraComma {
   interface,
-  "noodles",
-  ,"other",
+  noodles,
+  ,other,
 };
 
-/* BUILD Error(Unexpected identifier "somename" after "{".) */
-/* ERROR Unexpected identifier "somename" after "{". */
+/* BUILD Error(Unexpected string "somename" after "{".) */
+/* ERROR Unexpected string "somename" after "{". */
 enum ExtraComma {
-  somename,
-  "noodles",
-  ,"other",
+  "somename",
+  noodles,
+  other,
 };
 
 /* BUILD Enum(MealType3) */
 enum MealType3 {
   /* BUILD EnumItem(rice) */
-  "rice",
+  rice = 1 << 1,
   /* BUILD EnumItem(noodles) */
-  "noodles",
+  noodles = 0x1 << 0x2,

[nfullagar1, 2013/07/01 17:22:13]

what is expected outcome for octal?

[noelallen1, 2013/07/01 17:46:06]

Octal should be legal, although we never use it.  I can add a test case for it
here.

The lexer distinguishes between boolean, int, float, and string literals, but
does not distinguish between base 8, 10, or 16, they are all ints.

The parser never computes values of expressions, simply determines that the
expression is a valid int and adds a property pair to the EnumItem:
  TYPE = "integer"
  VALUE = "1", "1.0", "123", "0x123" or even "1 << 1"

   /* BUILD EnumItem(other) */
-  "other"
+  other = 0
 };