Introduce toV8NoInline

Source/bindings/scripts/code_generator_v8.pm

Index: Source/bindings/scripts/code_generator_v8.pm
diff --git a/Source/bindings/scripts/code_generator_v8.pm b/Source/bindings/scripts/code_generator_v8.pm
index 2bdd440753d9592507703936591aa7576267375e..5dbe36753fa5df648e3caf1f1b9769c3b0b38fb5 100644
--- a/Source/bindings/scripts/code_generator_v8.pm
+++ b/Source/bindings/scripts/code_generator_v8.pm
@@ -4752,6 +4752,16 @@ void ${v8ClassName}::derefObject(void* object)
 }
 
 END
+    if (!$interface->extendedAttributes->{"DoNotGenerateToV8"} && !$interface->extendedAttributes->{"CustomToV8"}) {

[haraken, 2013/11/23 15:03:18]

Probably we can auto-generate toV8NoInline when [CustomToV8] is specified. Then
you can avoid hand-writing toV8NoInline in V8ArrayBufferCustom.cpp.

[yhirano, 2013/11/25 01:50:52]

ConsoleBase has toV8Custom attribute but the custom toV8 function is not
defined, so generating toV8NoInline for it causes a link error with DEBUG mode.
Should we fix ConsoleBase?

[haraken, 2013/11/25 02:39:23]

Yes! It won't make sense to have [toV8Custom] but doesn't have a custom toV8
function.

[yhirano, 2013/11/25 03:36:49]

Done.
We can't omit toV8NoInline in V8ArrayBufferCustom.cpp because V8ArrayBuffer is
not generated by the generator.

+        $implementation{nameSpaceWebCore}->add(<<END);
+template<>
+v8::Handle<v8::Value> toV8NoInline(${nativeType}* impl, v8::Handle<v8::Object> creationContext, v8::Isolate* isolate)
+{
+    return toV8(impl, creationContext, isolate);
+}
+
+END
+    }
 }
 
 sub GenerateHeaderContentHeader