Changes between Version 152 and Version 153 of WebKitIDL


Ignore:
Timestamp:
Aug 2, 2016 12:12:39 PM (5 years ago)
Author:
Chris Dumez
Comment:

StrictTypeChecking no longer exists as of r204033

Legend:

Unmodified
Added
Removed
Modified
  • WebKitIDL

    v152 v153  
    1313 - [#CustomBinding CustomBinding][[br]]
    1414 - [#CallWith CallWith(m,a), SetterCallWith(a)][[br]]
    15  - [#StrictTypeChecking StrictTypeChecking(m,a,p)][[br]]
    1615 - [#NewObject NewObject(m,a)][[br]]
    1716 - [#ImplementedAs ImplementedAs(m,a)][[br]]
     
    414413For example, in case of `func4(...)`, `HTMLFoo::func3(ScriptArguments* arguments, ScriptCallStack* callstack, int a, int b)` is called in WebCore.
    415414
    416 == `[StrictTypeChecking]`(m,a,p) FIXME == #StrictTypeChecking
    417 
    418 Summary: ADD SUMMARY
    419 
    420 Usage: `[StrictTypeChecking]` can be specified on methods and attributes:
    421 {{{
    422     [StringTypeChecking] attribute float x;
    423     [StrictTypeChecking] DOMString func();
    424 }}}
    425 
    426 ADD EXPLANATIONS
    427 
    428 JSC: `[StrictTypeChecking]` can also be applied to a DOMString parameter in an overloaded method to make the
    429 overload resolution only match for ECMAScript types null, undefined, string or object - and not number or boolean.
    430 This is to permit overloads which are not "distinguishable" in WebIDL, for example:
    431 
    432 {{{
    433     interface CanvasFoo {
    434         void setColor([StrictTypeChecking] DOMString color);
    435         void setColor(float grayLevel);
    436     };
    437 }}}
    438 
    439415== `[NewObject]`(m,a) == #NewObject
    440416