Bug 81852 - run-bindings-tests output a lot of errors in TestSerializedScriptValueInterface.idl
Summary: run-bindings-tests output a lot of errors in TestSerializedScriptValueInterfa...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Kentaro Hara
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-21 17:52 PDT by Kentaro Hara
Modified: 2012-03-22 16:08 PDT (History)
4 users (show)

See Also:


Attachments
Patch (8.15 KB, patch)
2012-03-21 18:01 PDT, Kentaro Hara
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kentaro Hara 2012-03-21 17:52:33 PDT
run-bindings-tests output a lot of errors in TestSerializedScriptValueInterface.idl:

Use of uninitialized value in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 2743.
Use of uninitialized value $name in substitution (s///) at WebCore/bindings/scripts/CodeGenerator.pm line 119.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 2969.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 2972.
Use of uninitialized value $type in hash element at WebCore/bindings/scripts/CodeGenerator.pm line 367.
Use of uninitialized value $type in hash element at WebCore/bindings/scripts/CodeGenerator.pm line 368.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 2981.
Use of uninitialized value $type in hash element at WebCore/bindings/scripts/CodeGenerator.pm line 377.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 3004.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 3008.
Use of uninitialized value $type in pattern match (m//) at WebCore/bindings/scripts/CodeGenerator.pm line 453.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 3020.
Use of uninitialized value $type in pattern match (m//) at WebCore/bindings/scripts/CodeGeneratorJS.pm line 3026.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 3031.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 3031.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 3034.
Use of uninitialized value $type in concatenation (.) or string at WebCore/bindings/scripts/CodeGeneratorJS.pm line 3038.
Use of uninitialized value $type in string eq at WebCore/bindings/scripts/CodeGeneratorJS.pm line 321.

This is because [Constructor(...)] does not yet support [Optional] arguments. It just supports [Optional=DefaultIsUndefined] and [Optional=DefaultIsNullValue] arguments (as commented in CodeGeneratorJS.pm:3584).
Comment 1 Kentaro Hara 2012-03-21 18:01:46 PDT
Created attachment 133158 [details]
Patch
Comment 2 WebKit Review Bot 2012-03-22 16:08:32 PDT
Comment on attachment 133158 [details]
Patch

Clearing flags on attachment: 133158

Committed r111779: <http://trac.webkit.org/changeset/111779>
Comment 3 WebKit Review Bot 2012-03-22 16:08:36 PDT
All reviewed patches have been landed.  Closing bug.