Move chrome.downloads out of experimental to dev

ppapi/generators/idl_parser.py

Index: ppapi/generators/idl_parser.py
diff --git a/ppapi/generators/idl_parser.py b/ppapi/generators/idl_parser.py
index f1045c3bd0f7d23f2f9fe95830a971bd7c8b5b34..e4cdb9c36f942988fb5b1593878e5f5d6aeb06c4 100755
--- a/ppapi/generators/idl_parser.py
+++ b/ppapi/generators/idl_parser.py
@@ -221,6 +221,12 @@ class IDLParser(IDLLexer):
     p[0] = ListFromConcat(Copyright, Filedoc, p[3], p[4])
     if self.parse_debug: DumpReduction('top', p)
 
+  def p_top_short(self, p):
+    """top : COMMENT ext_attr_block top_list"""
+    Copyright = self.BuildComment('Copyright', p, 1)
+    p[0] = ListFromConcat(Copyright, p[2], p[3])

[asargent_no_longer_on_chrome, 2012/06/07 00:18:08]

Unfortunately there are some specific assumptions about the parse tree of some
Pepper API IDL files that I think this change might break. I agree with kalman
that we probably want to keep overview documentation in the .html files and just
use comments in the .idl file for narrow plaintext documentation of specific
functions/parameters/objects. 

[benjhayden, 2012/06/08 16:41:52]

I moved the documentation back into the html file, but there would still be
TODOs in IDL files about this issue if I removed p_top_short().

Note that p_top_short() does not replace p_top(), so ppapi IDLs can continue to
use and rely on filedocs.

Do I really need to remove p_top_short()? If so, can you elaborate?

+    if self.parse_debug: DumpReduction('top', p)
+
   # Build a list of top level items.
   def p_top_list(self, p):
     """top_list : callback_decl top_list
@@ -501,6 +507,11 @@ class IDLParser(IDLLexer):
     p[0] = p[1]
     if self.parse_debug: DumpReduction('expression_integer', p)
 
+  def p_expression_float(self, p):
+    "expression : FLOAT"
+    p[0] = p[1]
+    if self.parse_debug: DumpReduction('expression_float', p)
+
 #
 # Array List
 #