Add experimental.alarms API to allow lazy background pages to

chrome/renderer/extensions/schema_generated_bindings.cc

Index: chrome/renderer/extensions/schema_generated_bindings.cc
diff --git a/chrome/renderer/extensions/schema_generated_bindings.cc b/chrome/renderer/extensions/schema_generated_bindings.cc
index 525c0e8b48e2e9258767cd1ebba9fbd22f411f61..efd1c31657d2ad8644e89056e2bff0562443c9ed 100644
--- a/chrome/renderer/extensions/schema_generated_bindings.cc
+++ b/chrome/renderer/extensions/schema_generated_bindings.cc
@@ -141,7 +141,8 @@ class ExtensionImpl : public ChromeV8Extension {
     const std::set<std::string>& function_names =
         v8_extension->extension_dispatcher_->function_names();
     if (function_names.find(name) == function_names.end()) {
-      NOTREACHED() << "Unexpected function " << name;
+      NOTREACHED() << "Unexpected function " << name <<
+          ". Did you remember to register it with ExtensionFunctionRegistry?";

[Aaron Boodman, 2012/03/28 03:36:18]

Heh.

Can we automate registration?

[Mihai Parparita -not on Chrome, 2012/03/28 17:01:31]

I thought Mike and Antony's IDL work automates that step
(http://crrev.com/127159)

[Matt Perry, 2012/03/28 20:21:36]

Ah, cool, it does. Unfortunately it doesn't quite work with all the JSON files
yet:
- it generates the schema.json data, which is unnecessary for JSON files.
- it assumes a particular naming scheme for ExtensionFunctions, which is not
obeyed by all the JSON APIs.

       return v8::Undefined();
     }