bindings: Adds DOMArrayBuffer, etc. as thin wrappers for ArrayBuffer, etc.

Source/bindings/scripts/code_generator_v8.py

Index: Source/bindings/scripts/code_generator_v8.py
diff --git a/Source/bindings/scripts/code_generator_v8.py b/Source/bindings/scripts/code_generator_v8.py
index 065873d90fd04bc2e58ffdbd3c2af4639b780cd0..a493bd42373a3f495949f02ce4ae4a69dbc7d438 100644
--- a/Source/bindings/scripts/code_generator_v8.py
+++ b/Source/bindings/scripts/code_generator_v8.py
@@ -168,7 +168,10 @@ class CodeGeneratorV8(CodeGeneratorBase):
 
         template_context = interface_context(interface)
         # Add the include for interface itself
-        template_context['header_includes'].add(interface_info['include_path'])
+        if IdlType(interface_name).is_typed_array_element_type:

[bashi, 2014/10/14 23:36:24]

Can't we move this into interface_context() in v8_interface.py?

[Yuki, 2014/10/15 09:35:23]

It seems that |interface_info| is not available in IdlInterface and we cannot
retrieve 'include_path' there.  If it's possible, let me know.

Or, we can make it possible in a separate CL.

[bashi, 2014/10/15 10:17:33]

Ah, I see. I don't think we have a policy that we shouldn't pass interface_info
to interface_context(), but I don't have strong opinion here.

+            template_context['header_includes'].add('core/dom/DOMTypedArray.h')
+        else:
+            template_context['header_includes'].add(interface_info['include_path'])
         header_text, cpp_text = render_template(
             interface_info, header_template, cpp_template, template_context)
         header_path, cpp_path = self.output_paths(interface_name)