Rename toV8(...) function in Blink to ToV8(...).

third_party/WebKit/Source/bindings/IDLExtendedAttributes.md

 # Blink IDL Extended Attributes
 
 [TOC]
 
 ## Introduction
 
 The main interest in extended attributes are their _semantics_: Blink implements many more extended attributes than the Web IDL standard, to specify various behavior.
 
 The authoritative list of allowed extended attributes and values is [bindings/IDLExtendedAttributes.txt](https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/bindings/IDLExtendedAttributes.txt). This is complete but not necessarily precise (there may be unused extended attributes or values), since validation is run on build, but coverage isn't checked.
 
@@ skipping 1317 matching lines @@
 ```webidl
 interface HTMLFoo {
     [CachedAttribute=isKeyDirty] attribute DOMString key;
     [CachedAttribute=isValueDirty] attribute SerializedScriptValue serializedValue;
 };
 ```
 
 Without `[CachedAttribute]`, the key getter works in the following way:
 
 1. HTMLFoo::key() is called in Blink.
-2. The result of HTMLFoo::key() is passed to toV8(), and is converted to a wrapped object.
+2. The result of HTMLFoo::key() is passed to ToV8(), and is converted to a wrapped object.
 3. The wrapped object is returned.
 
 In case where HTMLFoo::key() or the operation to wrap the result is costly, you can cache the wrapped object onto the DOM object. With CachedAttribute, the key getter works in the following way:
 
 1. If the wrapped object is cached, the cached wrapped object is returned. That's it.
 2. Otherwise, `HTMLFoo::key()` is called in Blink.
-3. The result of `HTMLFoo::key()` is passed to `toV8()`, and is converted to a wrapped object.
+3. The result of `HTMLFoo::key()` is passed to `ToV8()`, and is converted to a wrapped object.
 4. The wrapped object is cached.
 5. The wrapped object is returned.
 
 `[CachedAttribute]` is particularly useful for serialized values, since deserialization can be costly. Without `[CachedAttribute]`, the serializedValue getter works in the following way:
 
 1. `HTMLFoo::serializedValue()` is called in Blink.
 2. The result of `HTMLFoo::serializedValue()` is deserialized.
-3. The deserialized result is passed to `toV8()`, and is converted to a wrapped object.
+3. The deserialized result is passed to `ToV8()`, and is converted to a wrapped object.
 4. The wrapped object is returned.
 
 In case where `HTMLFoo::serializedValue()`, the deserialization or the operation to wrap the result is costly, you can cache the wrapped object onto the DOM object. With `[CachedAttribute]`, the serializedValue getter works in the following way:
 
 1. If the wrapped object is cached, the cached wrapped object is returned. That's it.
 2. Otherwise, `HTMLFoo::serializedValue()` is called in Blink.
 3. The result of `HTMLFoo::serializedValue()` is deserialized.
-4. The deserialized result is passed to `toJS()` or `toV8()`, and is converted to a wrapped object.
+4. The deserialized result is passed to `toJS()` or `ToV8()`, and is converted to a wrapped object.
 5. The wrapped object is cached.
 6. The wrapped object is returned.
 
 *** note
 You should cache attributes if and only if it is really important for performance. Not only does caching increase the DOM object size, but also it increases the overhead of "cache-miss"ed getters. In addition, setters always need to invalidate the cache.
 ***
 
 `[CachedAttribute]` takes a required parameter which the name of a method to call on the implementation object. The method should take void and return bool. Before the cached attribute is used, the method will be called. If the method returns true the cached value is not used, which will result in the accessor being called again. This allows the implementation to both gain the performance benefit of caching (when the conversion to a script value can be done lazily) while allowing the value to be updated. The typical use pattern is:
 
 ```c++
@@ skipping 286 matching lines @@
 Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
 
 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
 
 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
 
 THIS SOFTWARE IS PROVIDED BY APPLE INC. AND ITS CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL APPLE INC. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 ***
 
 [CrossOriginProperties]: https://html.spec.whatwg.org/multipage/browsers.html#crossoriginproperties-(-o-)