IDL: Drop value conversion (V8 -> C++) macros from generated code

Source/bindings/core/v8/V8BindingMacros.h

Index: Source/bindings/core/v8/V8BindingMacros.h
diff --git a/Source/bindings/core/v8/V8BindingMacros.h b/Source/bindings/core/v8/V8BindingMacros.h
index 320cff6709bc0214451db6363bb4e03dfc294f1f..950977b785a93ba6b6428663387ac9b34e89767b 100644
--- a/Source/bindings/core/v8/V8BindingMacros.h
+++ b/Source/bindings/core/v8/V8BindingMacros.h
@@ -33,6 +33,14 @@
 
 namespace blink {
 
+#define TONATIVE_CONVERT(expression, bailout) \
+    if (!(expression))                        \
+        bailout;                              \
+
+#define TONATIVE_DECLARE(type, var, expression, bailout) \

[yhirano, 2015/02/24 03:51:24]

[optional] This is not a strong opinion, but I don't see a strong benefit of
this macro: In most (if not all) of occurrences, |expression| contains the
variable name (e.g. TONATIVE_DECLARE(V8StringResource<>, cppValue, (cppValue =
v8Value).prepare(exceptionState), return false)).

It doesn't save symbols from manual declaration with TONATIVE_CONVERT (e.g.
V8Stringresource<> cppValue; TONATIVE_CONVERT((cppValue =
v8Value).prepare(exceptionState), return false)). I feel the latter easier to
read.

[Jens Widell, 2015/02/24 07:31:43]

Essentially, I don't see a strong benefit to either of these macros. They are
effectively only here so that the Python scripts can provide single-line
"expression-like" code snippets for the Jinja templates to use.

If we were okay with the Python scripts generating (simple) multi-line code
snippets for the Jinja templates to use, we can easily get rid fo these macros
entirely.

+    type var;                                            \
+    TONATIVE_CONVERT(expression, bailout)
+
 // Naming scheme:
 // TO*_RETURNTYPE[_ARGTYPE]...
 // ...using _DEFAULT instead of _ANY..._ANY when returing a default value.