Changes between Version 125 and Version 126 of WebKitIDL

Timestamp:

Jun 12, 2013, 5:49:37 AM (12 years ago)

Author:

Christophe Dumez

Comment:

Rename [CallWith] to [ConstructorCallWith] for interfaces

WebKitIDL

@@ -13 +13 @@
  - [#Clamp Clamp(a,p)][[br]]
  - [#Custom Custom(m,a), CustomGetter(a), CustomSetter(a)][[br]]
- - [#CallWith CallWith(i,m,a)][[br]]
+ - [#CallWith CallWith(m,a)][[br]]
  - [#StrictTypeChecking StrictTypeChecking(m,a,p)][[br]]
  - [#ReturnNewObject ReturnNewObject(m,a)][[br]]
@@ -22 +22 @@
  - [#CachedAttribute CachedAttribute(a)][[br]]
  - [#JSWindowEventListener JSWindowEventListener(a)][[br]]
- - [#Constructor Constructor(i), CallWith(i,m,a), ConstructorRaisesException(i)][[br]]
+ - [#Constructor Constructor(i), ConstructorCallWith(i), ConstructorRaisesException(i)][[br]]
  - [#ConstructorTemplate ConstructorTemplate(i), InitializedByEventConstructor(a)][[br]]
  - [#NamedConstructor NamedConstructor(i)][[br]]
@@ -404 +404 @@
 Note: ObjC, GObject and CPP bindings do not support custom bindings.
 
-== `[CallWith]`(i,m,a) == #CallWith
+== `[CallWith]`(m,a) == #CallWith
 
 Summary: `[CallWith]` indicates that the bindings code calls a WebCore method with additional information.
@@ -421 +421 @@
 }}}
 
-Note: `[CallWith]` can be also specified on interfaces but it has a different meaning.
-Refer to [#Constructor the `[Constructor]` section] for `[CallWith]` on interfaces.
+Note: See `[ConstructorCallWith]` in the [#Constructor [Constructor] section] for similar functionality on constructors.
 
 In case of func1(...), HTMLFoo::func1(ScriptExecutionContext* context, int a, int b) is called in WebCore.
@@ -648 +647 @@
 ADD EXPLANATIONS
 
-== `[Constructor]`(i), `[CallWith]`(i,m,a), `[ConstructorRaisesException](i)` == #Constructor
+== `[Constructor]`(i), `[ConstructorCallWith]`(i), `[ConstructorRaisesException](i)` == #Constructor
 
  * [http://dev.w3.org/2006/webapi/WebIDL/#Constructor The spec of Constructor]
 
 Summary: `[Constructor]` indicates that the interface should have constructor, i.e. "new XXX()".
-`[CallWith]` and `[ConstructorRaisesException]` add information when the constructor callback is called in WebCore.
-
-Usage: `[Constructor]`, `[CallWith]` and `[ConstructorRaisesException]` can be specified on interfaces:
+`[ConstructorCallWith]` and `[ConstructorRaisesException]` add information when the constructor callback is called in WebCore.
+
+Usage: `[Constructor]`, `[ConstructorCallWith]` and `[ConstructorRaisesException]` can be specified on interfaces:
 {{{
     [
         Constructor(float x, float y, DOMString str),
         ConstructorRaisesException,
-        CallWith=ScriptExecutionContext
+        ConstructorCallWith=ScriptExecutionContext
     ] interface XXX {
     };
@@ -696 +695 @@
 
 If `XXX::create(...)` needs additional information like ScriptExecutionContext,
-you can specify `[CallWith=ScriptExecutionContext]`.
+you can specify `[ConstructorCallWith=ScriptExecutionContext]`.
 Then `XXX::create(...)` can have the following signature:
 {{{
@@ -705 +704 @@
 }}}
 You can retrieve document or frame from ScriptExecutionContext.
-Please see [#CallWith another [CallWith] section] for more details.
-
-Note that `[CallWith=...]` arguments are added at the head of `XXX::create(...)`'s arguments,
+
+Note that `[ConstructorCallWith=...]` arguments are added at the head of `XXX::create(...)`'s arguments,
 and the ExceptionCode argument is added at the tail of `XXX::create(...)`'s arguments.